Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f959533c4c248e39cdd7cc7bfcd63544cd978d85e1c99e0f95e47167d5fef85

Tx prefix hash: 8a28b69a0aa7375fe1acdc06420d3c05f98adeda9970f2ff77d345090e5582de
Tx public key: cb0927fc9d1e5850b78516f272ed0bb4dbc36364097a71a2409b06f2231d2a24
Timestamp: 1706082400 Timestamp [UCT]: 2024-01-24 07:46:40 Age [y:d:h:m:s]: 01:290:08:25:32
Block: 942146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466334 RingCT/type: yes/0
Extra: 01cb0927fc9d1e5850b78516f272ed0bb4dbc36364097a71a2409b06f2231d2a240211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7c0a2f8ba9f8ed38b05cce1c1792c854260c5389a9a99fa9f8c968cacd7a7db 0.600000000000 1400312 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": 942156, "vin": [ { "gen": { "height": 942146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7c0a2f8ba9f8ed38b05cce1c1792c854260c5389a9a99fa9f8c968cacd7a7db" } } ], "extra": [ 1, 203, 9, 39, 252, 157, 30, 88, 80, 183, 133, 22, 242, 114, 237, 11, 180, 219, 195, 99, 100, 9, 122, 113, 162, 64, 155, 6, 242, 35, 29, 42, 36, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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