Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 420b8bd75e8f017318bbec79e540f905267850949e656a571b4eae88bc826595

Tx prefix hash: 1a71b77e5ff70f92ce9cd3f7b05147a457919d5daa56d985629b9d6ff7e73ec4
Tx public key: a9bbf92e2aab8fd69f45857684596a5100fa7ef83fcee4af74686dc2e977087e
Timestamp: 1705181910 Timestamp [UCT]: 2024-01-13 21:38:30 Age [y:d:h:m:s]: 01:088:01:27:34
Block: 934693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324035 RingCT/type: yes/0
Extra: 01a9bbf92e2aab8fd69f45857684596a5100fa7ef83fcee4af74686dc2e977087e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d117d315bb1ff581683eb6a0bcfbaea5c8000a6c827a5560fc192b8730554d0c 0.600000000000 1392709 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": 934703, "vin": [ { "gen": { "height": 934693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d117d315bb1ff581683eb6a0bcfbaea5c8000a6c827a5560fc192b8730554d0c" } } ], "extra": [ 1, 169, 187, 249, 46, 42, 171, 143, 214, 159, 69, 133, 118, 132, 89, 106, 81, 0, 250, 126, 248, 63, 206, 228, 175, 116, 104, 109, 194, 233, 119, 8, 126, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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