Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 481a1d0bb450476df24a11db0bfc09a0878c9b3808c2b0769bf2615e2a950cf8

Tx prefix hash: 33717764df1f61ed0a66a8223bae2dfc2ab8e63e32bfb43cf41679f937fa9ccf
Tx public key: 7dac6cc7a07d7a555cd3bef8f79d319b23a06e84f960d832fee8bf1f6160e674
Timestamp: 1578921168 Timestamp [UCT]: 2020-01-13 13:12:48 Age [y:d:h:m:s]: 04:350:21:31:07
Block: 44631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140328 RingCT/type: yes/0
Extra: 017dac6cc7a07d7a555cd3bef8f79d319b23a06e84f960d832fee8bf1f6160e67402110000004049b77a3d000000000000000000

1 output(s) for total of 436.636272305000 dcy

stealth address amount amount idx
00: e790304f42fcb5de41ce2f60d040b063df4136724bbf4087e8f8074daf769987 436.636272305000 81276 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": 44641, "vin": [ { "gen": { "height": 44631 } } ], "vout": [ { "amount": 436636272305, "target": { "key": "e790304f42fcb5de41ce2f60d040b063df4136724bbf4087e8f8074daf769987" } } ], "extra": [ 1, 125, 172, 108, 199, 160, 125, 122, 85, 92, 211, 190, 248, 247, 157, 49, 155, 35, 160, 110, 132, 249, 96, 216, 50, 254, 232, 191, 31, 97, 96, 230, 116, 2, 17, 0, 0, 0, 64, 73, 183, 122, 61, 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