Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34993ca5b76b09fe6c6a33096e32aff6a43289da7223068773781df765cf5ae1

Tx prefix hash: 679881dc9bcc06ab6a68d8f48fe729c7bad07a6a3bb7553754a0ff0f41db436c
Tx public key: ec2dfb7da414428ca19685e7922acbcae1e06a66c238fe38021b1d58ec4189d5
Timestamp: 1724780909 Timestamp [UCT]: 2024-08-27 17:48:29 Age [y:d:h:m:s]: 00:239:04:00:36
Block: 1097176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170810 RingCT/type: yes/0
Extra: 01ec2dfb7da414428ca19685e7922acbcae1e06a66c238fe38021b1d58ec4189d5021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b043c888bed2f936bbc1b6c188d63c1b0c81ba0ab093da5098c16e9bde291b8 0.600000000000 1572507 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": 1097186, "vin": [ { "gen": { "height": 1097176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b043c888bed2f936bbc1b6c188d63c1b0c81ba0ab093da5098c16e9bde291b8" } } ], "extra": [ 1, 236, 45, 251, 125, 164, 20, 66, 140, 161, 150, 133, 231, 146, 42, 203, 202, 225, 224, 106, 102, 194, 56, 254, 56, 2, 27, 29, 88, 236, 65, 137, 213, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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