Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47d0792c469f2afe708598c2a5e09be648ecf0a6dc13178c86426547615d0083

Tx prefix hash: 0a35b61392188f11f4c5824fc3f5c72d7ddcb366f4a16eec86d1a959d50a9849
Tx public key: ceacd49edcd0a5765f4f99d3c0c54cac4386ae7290831d45f7353b46920a8c6d
Timestamp: 1717017446 Timestamp [UCT]: 2024-05-29 21:17:26 Age [y:d:h:m:s]: 01:168:22:59:28
Block: 1032831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379348 RingCT/type: yes/0
Extra: 01ceacd49edcd0a5765f4f99d3c0c54cac4386ae7290831d45f7353b46920a8c6d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50c8648d1749ba27a7003ff2176a5a5e3e1ef8a5f6070ebf2dd8fb28703319e2 0.600000000000 1501286 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": 1032841, "vin": [ { "gen": { "height": 1032831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50c8648d1749ba27a7003ff2176a5a5e3e1ef8a5f6070ebf2dd8fb28703319e2" } } ], "extra": [ 1, 206, 172, 212, 158, 220, 208, 165, 118, 95, 79, 153, 211, 192, 197, 76, 172, 67, 134, 174, 114, 144, 131, 29, 69, 247, 53, 59, 70, 146, 10, 140, 109, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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