Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 553a3305ca3deabc43895d160ba5d89e491faed91c2fdd54f4b50bcd9ef8f1e4

Tx prefix hash: 831a457571c9cfea730ac7f1ea9fbc5d65de57b7400eb8f8034b77dd3837b9ec
Tx public key: df305537c43734400e58f1ed3cc51f19da44d74b69cfbd0e3bc207b1f65f01a4
Timestamp: 1726971465 Timestamp [UCT]: 2024-09-22 02:17:45 Age [y:d:h:m:s]: 00:063:15:10:04
Block: 1115349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45480 RingCT/type: yes/0
Extra: 01df305537c43734400e58f1ed3cc51f19da44d74b69cfbd0e3bc207b1f65f01a402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d86b4967f78a6efdbe7a4e75a8d7a2c3ccc04114b89c39a87bc95da54443e334 0.600000000000 1595452 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": 1115359, "vin": [ { "gen": { "height": 1115349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d86b4967f78a6efdbe7a4e75a8d7a2c3ccc04114b89c39a87bc95da54443e334" } } ], "extra": [ 1, 223, 48, 85, 55, 196, 55, 52, 64, 14, 88, 241, 237, 60, 197, 31, 25, 218, 68, 215, 75, 105, 207, 189, 14, 59, 194, 7, 177, 246, 95, 1, 164, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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