Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f19cc0a87a498cace8579fa42ef80894cf400e83c3abdd139fe82a62406880d4

Tx prefix hash: 2ed1cf02d6d9efab56cbefb05a8345de22af4ed0873e1fef22a2d3216ee06cea
Tx public key: f21e09174f432c8019fe1491f0f54cb37c60a4dbd2f1e1f8c952ce589d29c257
Timestamp: 1738089428 Timestamp [UCT]: 2025-01-28 18:37:08 Age [y:d:h:m:s]: 00:044:17:58:56
Block: 1207117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32015 RingCT/type: yes/0
Extra: 01f21e09174f432c8019fe1491f0f54cb37c60a4dbd2f1e1f8c952ce589d29c2570211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a9e905a15f7786e1e37595a39b15b14b98b2af4be0724a259b4ceaf7f70728 0.600000000000 1693838 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": 1207127, "vin": [ { "gen": { "height": 1207117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a9e905a15f7786e1e37595a39b15b14b98b2af4be0724a259b4ceaf7f70728" } } ], "extra": [ 1, 242, 30, 9, 23, 79, 67, 44, 128, 25, 254, 20, 145, 240, 245, 76, 179, 124, 96, 164, 219, 210, 241, 225, 248, 201, 82, 206, 88, 157, 41, 194, 87, 2, 17, 0, 0, 0, 3, 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