Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3199c73f89195448e984010a7e12be93085444de21605a5b4dd73b2b9ae5d5a3

Tx prefix hash: 52643d6bc8a92b9c89875ab7478b28325ef4398afca81182a461d7c021960537
Tx public key: 48fced8f4dd537b1c0feebbc5d44d632a09ac0fd6fd3b583a441970ddc56cffb
Timestamp: 1726908516 Timestamp [UCT]: 2024-09-21 08:48:36 Age [y:d:h:m:s]: 00:064:05:20:20
Block: 1114830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45908 RingCT/type: yes/0
Extra: 0148fced8f4dd537b1c0feebbc5d44d632a09ac0fd6fd3b583a441970ddc56cffb021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 775488789ba5ec2428a01ed292d9189f3b3f0a6178e4fa56e6626810bc4afc0d 0.600000000000 1594747 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": 1114840, "vin": [ { "gen": { "height": 1114830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "775488789ba5ec2428a01ed292d9189f3b3f0a6178e4fa56e6626810bc4afc0d" } } ], "extra": [ 1, 72, 252, 237, 143, 77, 213, 55, 177, 192, 254, 235, 188, 93, 68, 214, 50, 160, 154, 192, 253, 111, 211, 181, 131, 164, 65, 151, 13, 220, 86, 207, 251, 2, 17, 0, 0, 0, 5, 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