Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f62bbf76f5c59c9f277550265b81a329b1b499123ef591e919f0d97bbc82a7b

Tx prefix hash: ac842f582b792577cabf3c657e7caa3af84e7b260a136d05bac0934853ebaddb
Tx public key: 6918d4a2057389b6d133fab5181ffbdb20e434b192e3b7587eedcb9c8d96d999
Timestamp: 1729013977 Timestamp [UCT]: 2024-10-15 17:39:37 Age [y:d:h:m:s]: 00:099:19:34:42
Block: 1132289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71300 RingCT/type: yes/0
Extra: 016918d4a2057389b6d133fab5181ffbdb20e434b192e3b7587eedcb9c8d96d999021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dfd17596cae7e98dcc65bbeacab748ad84c1006ebd6d3ea5b9a125c8e2d8a99 0.600000000000 1615202 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": 1132299, "vin": [ { "gen": { "height": 1132289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dfd17596cae7e98dcc65bbeacab748ad84c1006ebd6d3ea5b9a125c8e2d8a99" } } ], "extra": [ 1, 105, 24, 212, 162, 5, 115, 137, 182, 209, 51, 250, 181, 24, 31, 251, 219, 32, 228, 52, 177, 146, 227, 183, 88, 126, 237, 203, 156, 141, 150, 217, 153, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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