Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53fa3161e58050a8ae1bbe023446621b90dbf649efd13b41a489d6252f629d92

Tx prefix hash: 7173143c5d3f68d89a725c991197b342878b101b4bf5941dccd4f6dda3701f8d
Tx public key: e47b0eec6d1a5db1baf7a0618f39516c4116e3a453f97363ce417d1f32d41a22
Timestamp: 1675497015 Timestamp [UCT]: 2023-02-04 07:50:15 Age [y:d:h:m:s]: 01:357:22:23:58
Block: 689485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516562 RingCT/type: yes/0
Extra: 01e47b0eec6d1a5db1baf7a0618f39516c4116e3a453f97363ce417d1f32d41a22021100000002272bcc39000000000000000000

1 output(s) for total of 3.187497882000 dcy

stealth address amount amount idx
00: fdfbd5e4f23ebf4c0fc59958ef7b995413725e0755a07a5683662140ee7d3d69 3.187497882000 1132161 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": 689495, "vin": [ { "gen": { "height": 689485 } } ], "vout": [ { "amount": 3187497882, "target": { "key": "fdfbd5e4f23ebf4c0fc59958ef7b995413725e0755a07a5683662140ee7d3d69" } } ], "extra": [ 1, 228, 123, 14, 236, 109, 26, 93, 177, 186, 247, 160, 97, 143, 57, 81, 108, 65, 22, 227, 164, 83, 249, 115, 99, 206, 65, 125, 31, 50, 212, 26, 34, 2, 17, 0, 0, 0, 2, 39, 43, 204, 57, 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