Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19a4bd6345a9719f682a243fe5bf3f0831547cda385416ea257eb996ca9f6072

Tx prefix hash: 35617cf28535368523682f9e030d636b2132c48b7c19bcdb22aa0e38cfa30114
Tx public key: 41d86da826c3e7a6bcb0f6fa81ee13fe901b2c36d16c7cc84d5e922ff586bac1
Timestamp: 1662990941 Timestamp [UCT]: 2022-09-12 13:55:41 Age [y:d:h:m:s]: 02:190:05:23:18
Block: 586359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 657260 RingCT/type: yes/0
Extra: 0141d86da826c3e7a6bcb0f6fa81ee13fe901b2c36d16c7cc84d5e922ff586bac1021100000001dedc788d000000000000000000

1 output(s) for total of 7.000826307000 dcy

stealth address amount amount idx
00: 02ad7cd3393fb0f14f58df12aec867bf8b95ea611390fa69a55b1e6730c1c3e0 7.000826307000 1020462 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": 586369, "vin": [ { "gen": { "height": 586359 } } ], "vout": [ { "amount": 7000826307, "target": { "key": "02ad7cd3393fb0f14f58df12aec867bf8b95ea611390fa69a55b1e6730c1c3e0" } } ], "extra": [ 1, 65, 216, 109, 168, 38, 195, 231, 166, 188, 176, 246, 250, 129, 238, 19, 254, 144, 27, 44, 54, 209, 108, 124, 200, 77, 94, 146, 47, 245, 134, 186, 193, 2, 17, 0, 0, 0, 1, 222, 220, 120, 141, 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