Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4783ab4050448aa9dd85d066c8588e0063b0115cea133eab247ba714ad8295

Tx prefix hash: 3405fe8a212d7e062de983162047111e85d04f0d01d4eea40d7fa4488af0012d
Tx public key: 6651ba822eff299f456bf9f44b20049e7e2de422ea16e938831224f4bb94be5e
Timestamp: 1713795590 Timestamp [UCT]: 2024-04-22 14:19:50 Age [y:d:h:m:s]: 00:353:14:35:43
Block: 1006116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252796 RingCT/type: yes/0
Extra: 016651ba822eff299f456bf9f44b20049e7e2de422ea16e938831224f4bb94be5e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88707ef7d4e46439a549a3aa8a39a3f51e97b09a59a69ed0bf40bb3b8a88d2d5 0.600000000000 1467038 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": 1006126, "vin": [ { "gen": { "height": 1006116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88707ef7d4e46439a549a3aa8a39a3f51e97b09a59a69ed0bf40bb3b8a88d2d5" } } ], "extra": [ 1, 102, 81, 186, 130, 46, 255, 41, 159, 69, 107, 249, 244, 75, 32, 4, 158, 126, 45, 228, 34, 234, 22, 233, 56, 131, 18, 36, 244, 187, 148, 190, 94, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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