Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80e3d99be6d85639bbb139c1eb054b20f0f64a91ac5f49de803476ea6474b132

Tx prefix hash: bd1f08d8df0d3071ecad4fb1e1c960d59ac5c58588ac6c3d0b792e7daaab2e3d
Tx public key: 7584e9bfdc27b6952608fad0b40c1cdf40b1af171226b0ad3db48c4513814f79
Timestamp: 1736238686 Timestamp [UCT]: 2025-01-07 08:31:26 Age [y:d:h:m:s]: 00:085:08:42:33
Block: 1192053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60778 RingCT/type: yes/0
Extra: 017584e9bfdc27b6952608fad0b40c1cdf40b1af171226b0ad3db48c4513814f790211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70ce08ec56e9f129a645c72fbd3e2fe5172bc2d854688de74eef37b971afdef3 0.600000000000 1678598 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": 1192063, "vin": [ { "gen": { "height": 1192053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70ce08ec56e9f129a645c72fbd3e2fe5172bc2d854688de74eef37b971afdef3" } } ], "extra": [ 1, 117, 132, 233, 191, 220, 39, 182, 149, 38, 8, 250, 208, 180, 12, 28, 223, 64, 177, 175, 23, 18, 38, 176, 173, 61, 180, 140, 69, 19, 129, 79, 121, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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