Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e00c981667b5cde744b25e71efa5638ec12cc5fd4d5b1ee1b5e34d353b6d243e

Tx prefix hash: 0754c98f13de38a8611c7e90fd5253db07a76ff135ed287f85b52ab563ef15ac
Tx public key: 262cf057e83e2bf75241506a1ab6e57aa600b9860ef970bd29bf44fb5758d576
Timestamp: 1644617480 Timestamp [UCT]: 2022-02-11 22:11:20 Age [y:d:h:m:s]: 02:334:07:44:33
Block: 436577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 758257 RingCT/type: yes/0
Extra: 01262cf057e83e2bf75241506a1ab6e57aa600b9860ef970bd29bf44fb5758d57602110000000abf7ee4e7000000000000000000

1 output(s) for total of 21.950249734000 dcy

stealth address amount amount idx
00: 4a5345ae21bb89cc21f7b209ec0698ce07df8c4ddd4ae483a448fe4db22e6cac 21.950249734000 847982 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": 436587, "vin": [ { "gen": { "height": 436577 } } ], "vout": [ { "amount": 21950249734, "target": { "key": "4a5345ae21bb89cc21f7b209ec0698ce07df8c4ddd4ae483a448fe4db22e6cac" } } ], "extra": [ 1, 38, 44, 240, 87, 232, 62, 43, 247, 82, 65, 80, 106, 26, 182, 229, 122, 166, 0, 185, 134, 14, 249, 112, 189, 41, 191, 68, 251, 87, 88, 213, 118, 2, 17, 0, 0, 0, 10, 191, 126, 228, 231, 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