Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acceac74a93e92ab478a0ef365e54a27fbc63982d5c9f4f695a9dd033151407c

Tx prefix hash: b2efb513a8da761007f78d7fbda6be429933f8d112cdcaa1edc1c80ac7073d33
Tx public key: 52e0a3158f5f0860de503c3d220ed138a2fde9b610f078991df1116147f6e07c
Timestamp: 1720620485 Timestamp [UCT]: 2024-07-10 14:08:05 Age [y:d:h:m:s]: 00:268:22:45:24
Block: 1062703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192150 RingCT/type: yes/0
Extra: 0152e0a3158f5f0860de503c3d220ed138a2fde9b610f078991df1116147f6e07c02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4cea570516891417ff8c0d70261ff2cd7c5ab45e98d01a669ab0ebc7b184f66 0.600000000000 1533210 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": 1062713, "vin": [ { "gen": { "height": 1062703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4cea570516891417ff8c0d70261ff2cd7c5ab45e98d01a669ab0ebc7b184f66" } } ], "extra": [ 1, 82, 224, 163, 21, 143, 95, 8, 96, 222, 80, 60, 61, 34, 14, 209, 56, 162, 253, 233, 182, 16, 240, 120, 153, 29, 241, 17, 97, 71, 246, 224, 124, 2, 17, 0, 0, 0, 8, 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