Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18822e8c4e61ff56e71dcd5c086154996b2f46f15e6e269d5984ef790a8c1c09

Tx prefix hash: 6ba44a007716633251331ef7be5b3c99e64d04eaa17c7a575318a895c091c5d5
Tx public key: 1515ce1b1632cf4eb6dbcfbee86049e7b4593cc3714a3d57e3c00aab7cf9c341
Timestamp: 1724094694 Timestamp [UCT]: 2024-08-19 19:11:34 Age [y:d:h:m:s]: 00:232:21:25:28
Block: 1091511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166310 RingCT/type: yes/0
Extra: 011515ce1b1632cf4eb6dbcfbee86049e7b4593cc3714a3d57e3c00aab7cf9c34102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21272b92faed8b75b7b0e61fcdbbd28bf47a7653c9828926807ec3d4c99712ea 0.600000000000 1566144 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": 1091521, "vin": [ { "gen": { "height": 1091511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21272b92faed8b75b7b0e61fcdbbd28bf47a7653c9828926807ec3d4c99712ea" } } ], "extra": [ 1, 21, 21, 206, 27, 22, 50, 207, 78, 182, 219, 207, 190, 232, 96, 73, 231, 180, 89, 60, 195, 113, 74, 61, 87, 227, 192, 10, 171, 124, 249, 195, 65, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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