Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b78758003275e171f2c5b4722f9f9a1efc58327a08ad0289e4398ea092dafd00

Tx prefix hash: bb92c3507f782a0d43d9be78b2dc2e0756058edf658ffa1baedf0b8531161aff
Tx public key: 176f785a5577ea90fb8647ced1036d4d0c69fd6ae6009118a4dc370834f80a08
Timestamp: 1655235018 Timestamp [UCT]: 2022-06-14 19:30:18 Age [y:d:h:m:s]: 02:210:09:02:57
Block: 522429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 671638 RingCT/type: yes/0
Extra: 01176f785a5577ea90fb8647ced1036d4d0c69fd6ae6009118a4dc370834f80a0802110000000175e3f0e9000000000000000000

1 output(s) for total of 11.401868426000 dcy

stealth address amount amount idx
00: 400ae494939f34ca73e5a59e234f0af33a2f3293a9a463ed4c660382209cf2cc 11.401868426000 950452 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": 522439, "vin": [ { "gen": { "height": 522429 } } ], "vout": [ { "amount": 11401868426, "target": { "key": "400ae494939f34ca73e5a59e234f0af33a2f3293a9a463ed4c660382209cf2cc" } } ], "extra": [ 1, 23, 111, 120, 90, 85, 119, 234, 144, 251, 134, 71, 206, 209, 3, 109, 77, 12, 105, 253, 106, 230, 0, 145, 24, 164, 220, 55, 8, 52, 248, 10, 8, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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