Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b1ef7c008c284363fd5b2785a8570130adffe832cd026d05fbeb4c7f14fb72b

Tx prefix hash: b7075ef843ad1a0c10d194a6f3f133cbadc762fe797ca526879490a5f42e81f1
Tx public key: fd1540a8eed44f48f437a3a11e566f8a679e02e00bc294bfdea5750a85a4c424
Timestamp: 1703247082 Timestamp [UCT]: 2023-12-22 12:11:22 Age [y:d:h:m:s]: 01:116:08:33:37
Block: 918668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344283 RingCT/type: yes/0
Extra: 01fd1540a8eed44f48f437a3a11e566f8a679e02e00bc294bfdea5750a85a4c42402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2c769898b4811f68da1a66e458fe133e7ca68ad4c9140800a8d68113efbc93a 0.600000000000 1376320 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": 918678, "vin": [ { "gen": { "height": 918668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2c769898b4811f68da1a66e458fe133e7ca68ad4c9140800a8d68113efbc93a" } } ], "extra": [ 1, 253, 21, 64, 168, 238, 212, 79, 72, 244, 55, 163, 161, 30, 86, 111, 138, 103, 158, 2, 224, 11, 194, 148, 191, 222, 165, 117, 10, 133, 164, 196, 36, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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