Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed1bad577e9ca1c1bc93e3825ef48b131f3d7bc6f6d2fdd6d2ee50a96054e106

Tx prefix hash: eaa88c6bc4838dc18cbeeecd751a35e26c43d5a4855c2a1034a2532682fd8706
Tx public key: 5b84082e0ed3e5bdfb5c7dd71666a9138610ec4f870135392008dbcf9dc01983
Timestamp: 1657125926 Timestamp [UCT]: 2022-07-06 16:45:26 Age [y:d:h:m:s]: 02:185:05:36:51
Block: 537997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653741 RingCT/type: yes/0
Extra: 015b84082e0ed3e5bdfb5c7dd71666a9138610ec4f870135392008dbcf9dc019830211000000074da16a3a000000000000000000

1 output(s) for total of 10.124946933000 dcy

stealth address amount amount idx
00: 5b9f7004193b223591655bd7e708cc9f97aac611d33c5d078a14e1c73077b147 10.124946933000 967944 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": 538007, "vin": [ { "gen": { "height": 537997 } } ], "vout": [ { "amount": 10124946933, "target": { "key": "5b9f7004193b223591655bd7e708cc9f97aac611d33c5d078a14e1c73077b147" } } ], "extra": [ 1, 91, 132, 8, 46, 14, 211, 229, 189, 251, 92, 125, 215, 22, 102, 169, 19, 134, 16, 236, 79, 135, 1, 53, 57, 32, 8, 219, 207, 157, 192, 25, 131, 2, 17, 0, 0, 0, 7, 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