Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 899d51db3442c9d77b17de5ccf9b90422633dd96e5b3f5897b98f801836b59e9

Tx prefix hash: 77fc4710e856943a829b80dbfb0d9284c24e3cfb3af5fa6d8a514c7ea934e46d
Tx public key: 9c11836327f38031e948e6864f3c95e3c2d1b75cbf0ed595eaa2dac7162e6f05
Timestamp: 1582036422 Timestamp [UCT]: 2020-02-18 14:33:42 Age [y:d:h:m:s]: 05:015:22:26:20
Block: 67586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164388 RingCT/type: yes/0
Extra: 019c11836327f38031e948e6864f3c95e3c2d1b75cbf0ed595eaa2dac7162e6f050211000000030aca7173000000000000000000

1 output(s) for total of 366.488484319000 dcy

stealth address amount amount idx
00: 7dde05e8e3f9aa86ead117486e2cc55d27eebc955675ef71cc3a2c9512fc26b9 366.488484319000 124469 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": 67596, "vin": [ { "gen": { "height": 67586 } } ], "vout": [ { "amount": 366488484319, "target": { "key": "7dde05e8e3f9aa86ead117486e2cc55d27eebc955675ef71cc3a2c9512fc26b9" } } ], "extra": [ 1, 156, 17, 131, 99, 39, 243, 128, 49, 233, 72, 230, 134, 79, 60, 149, 227, 194, 209, 183, 92, 191, 14, 213, 149, 234, 162, 218, 199, 22, 46, 111, 5, 2, 17, 0, 0, 0, 3, 10, 202, 113, 115, 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