Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1cdbeda8d7945a497a8278c9104298e1e4a0992c425e7a20b160890a21d47639

Tx prefix hash: 20c22819d02cb71b50bcf822a5bb68db93b7c0f80ab47018268e159bfb747e5f
Tx public key: 80d3c545c9ab6b256f6cf819c4c6cb8d964dc1f521262bf5d199d8df44b002fe
Timestamp: 1581935641 Timestamp [UCT]: 2020-02-17 10:34:01 Age [y:d:h:m:s]: 04:262:23:53:25
Block: 66571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080458 RingCT/type: yes/0
Extra: 0180d3c545c9ab6b256f6cf819c4c6cb8d964dc1f521262bf5d199d8df44b002fe02110000001a4943cd9f000000000000000000

1 output(s) for total of 369.369128771000 dcy

stealth address amount amount idx
00: 5d8606e3a58c74787438bca6a75781947cff69e0abfe5bb3a4acc6175e1aafa2 369.369128771000 122654 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 66581, "vin": [ { "gen": { "height": 66571 } } ], "vout": [ { "amount": 369369128771, "target": { "key": "5d8606e3a58c74787438bca6a75781947cff69e0abfe5bb3a4acc6175e1aafa2" } } ], "extra": [ 1, 128, 211, 197, 69, 201, 171, 107, 37, 111, 108, 248, 25, 196, 198, 203, 141, 150, 77, 193, 245, 33, 38, 43, 245, 209, 153, 216, 223, 68, 176, 2, 254, 2, 17, 0, 0, 0, 26, 73, 67, 205, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8