Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e314e456758ad906af9dfef4d46d2990e9bf58aa0168a18cb90b827963c2f1c

Tx prefix hash: c99d05fa22dadea8149c4fae20b57d361d629847878cce5e6d9ab2873d467310
Tx public key: 6a373f248a867abe1411544943979a631f3f1bcd20d15cece84f70c1a93f2da4
Timestamp: 1724079941 Timestamp [UCT]: 2024-08-19 15:05:41 Age [y:d:h:m:s]: 00:208:19:58:27
Block: 1091387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149120 RingCT/type: yes/0
Extra: 016a373f248a867abe1411544943979a631f3f1bcd20d15cece84f70c1a93f2da402110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5fd4f48883fee1db433c060aa916d8c93fb259ae56e7091c7b8fd3c552602ff 0.600000000000 1566018 of 15

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": 1091397, "vin": [ { "gen": { "height": 1091387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5fd4f48883fee1db433c060aa916d8c93fb259ae56e7091c7b8fd3c552602ff" } } ], "extra": [ 1, 106, 55, 63, 36, 138, 134, 122, 190, 20, 17, 84, 73, 67, 151, 154, 99, 31, 63, 27, 205, 32, 209, 92, 236, 232, 79, 112, 193, 169, 63, 45, 164, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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