Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de9bb3c18839e23f2207b16badbcde9155b67384efb1a45df218f9687f0f0da6

Tx prefix hash: b6dba38abbcd55620a84475f1fa0f7c51a00fdd5a208749dd94fc485d04cdc16
Tx public key: cb5c57188000fae19df8b1be58ddbdcedfb3f53a168dc0bf672a4b6a33628476
Timestamp: 1652029140 Timestamp [UCT]: 2022-05-08 16:59:00 Age [y:d:h:m:s]: 02:181:08:48:26
Block: 496867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649895 RingCT/type: yes/0
Extra: 01cb5c57188000fae19df8b1be58ddbdcedfb3f53a168dc0bf672a4b6a336284760211000000064da16a3a000000000000000000

1 output(s) for total of 13.857139205000 dcy

stealth address amount amount idx
00: 36666d9cc565ed14e7b32ebfbf7d8e6e34b23f01c6674a0be28c275ceba805f5 13.857139205000 920876 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": 496877, "vin": [ { "gen": { "height": 496867 } } ], "vout": [ { "amount": 13857139205, "target": { "key": "36666d9cc565ed14e7b32ebfbf7d8e6e34b23f01c6674a0be28c275ceba805f5" } } ], "extra": [ 1, 203, 92, 87, 24, 128, 0, 250, 225, 157, 248, 177, 190, 88, 221, 189, 206, 223, 179, 245, 58, 22, 141, 192, 191, 103, 42, 75, 106, 51, 98, 132, 118, 2, 17, 0, 0, 0, 6, 77, 161, 106, 58, 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