Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 499d4de0552f5fa75a8e045cb4ada8878e1dcd3c022eed7d13d63b2976a16071

Tx prefix hash: 1e26d5e3482a3bad2acfae7d3a3d7a0f6113eb2abd5e6d50a889ef67f0655bd7
Tx public key: 41c17a8ae6e07db22f64af68d0161698ce32588243d73525b37ddf765f066cae
Timestamp: 1721138150 Timestamp [UCT]: 2024-07-16 13:55:50 Age [y:d:h:m:s]: 00:205:14:18:03
Block: 1067007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146832 RingCT/type: yes/0
Extra: 0141c17a8ae6e07db22f64af68d0161698ce32588243d73525b37ddf765f066cae021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f67d75e2ba61d44d23d23b763dd557c24d18e62867b87f1c9c383ae89996226 0.600000000000 1537704 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": 1067017, "vin": [ { "gen": { "height": 1067007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f67d75e2ba61d44d23d23b763dd557c24d18e62867b87f1c9c383ae89996226" } } ], "extra": [ 1, 65, 193, 122, 138, 230, 224, 125, 178, 47, 100, 175, 104, 208, 22, 22, 152, 206, 50, 88, 130, 67, 215, 53, 37, 179, 125, 223, 118, 95, 6, 108, 174, 2, 17, 0, 0, 0, 16, 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