Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ede6dae58dabf37ee0ae2eb10815829a4dcbc81c3c34dfaef6ff9034562a6b66

Tx prefix hash: f3f363d2b0d8219ea954c04d214163744ac6c38fde3735534032f06c683fbff7
Tx public key: c7db3403f8729ab6c5a8d4867c49b1244639499aa601c8cc6decdc904b5318b7
Timestamp: 1709766639 Timestamp [UCT]: 2024-03-06 23:10:39 Age [y:d:h:m:s]: 01:030:05:39:58
Block: 972719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282608 RingCT/type: yes/0
Extra: 01c7db3403f8729ab6c5a8d4867c49b1244639499aa601c8cc6decdc904b5318b702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81ae5c64e8624d3fafcf2970bd226e3eb2505de4e6c6839c884e54f1a99e1fb7 0.600000000000 1432638 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": 972729, "vin": [ { "gen": { "height": 972719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81ae5c64e8624d3fafcf2970bd226e3eb2505de4e6c6839c884e54f1a99e1fb7" } } ], "extra": [ 1, 199, 219, 52, 3, 248, 114, 154, 182, 197, 168, 212, 134, 124, 73, 177, 36, 70, 57, 73, 154, 166, 1, 200, 204, 109, 236, 220, 144, 75, 83, 24, 183, 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