Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63bbf2056b31b44c0dfe243b815feb562c085ea6972dd17f16ad1425d85ce418

Tx prefix hash: bbe49979813455d7a47fb6b17a2c83c96baeafdbdd72c34222489063dc9529dc
Tx public key: 9fc4d5cfa17e82f767ca51341964c6dd6667ac3646ea5bb08bf0422d2a0a3a36
Timestamp: 1674854541 Timestamp [UCT]: 2023-01-27 21:22:21 Age [y:d:h:m:s]: 02:123:07:42:00
Block: 684163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609808 RingCT/type: yes/0
Extra: 019fc4d5cfa17e82f767ca51341964c6dd6667ac3646ea5bb08bf0422d2a0a3a360211000000017e406890000000000000000000

1 output(s) for total of 3.319585875000 dcy

stealth address amount amount idx
00: 0f6d7d368c605970daf1f59eabaf4d5a3f01e60c11e7faf9a6815a9c17ddf6d2 3.319585875000 1126376 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": 684173, "vin": [ { "gen": { "height": 684163 } } ], "vout": [ { "amount": 3319585875, "target": { "key": "0f6d7d368c605970daf1f59eabaf4d5a3f01e60c11e7faf9a6815a9c17ddf6d2" } } ], "extra": [ 1, 159, 196, 213, 207, 161, 126, 130, 247, 103, 202, 81, 52, 25, 100, 198, 221, 102, 103, 172, 54, 70, 234, 91, 176, 139, 240, 66, 45, 42, 10, 58, 54, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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