Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed8c2193c54d60be095b5f4a2728483efa051981fb7d1372afae01e6731a929c

Tx prefix hash: dcbdab7507148ce17fbd1eb7e27a8227f851bdb5867c90a342c87373c04fda2e
Tx public key: 8c25e65b6d9311f38cadc607a72f43420199b672590f81eae96c7f4b90e7c907
Timestamp: 1712882284 Timestamp [UCT]: 2024-04-12 00:38:04 Age [y:d:h:m:s]: 00:359:11:50:06
Block: 998525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257019 RingCT/type: yes/0
Extra: 018c25e65b6d9311f38cadc607a72f43420199b672590f81eae96c7f4b90e7c90702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4563ec860f02fe7c9079f889e840a82feb57a9af8fbc4bdb997e050d7d3f294 0.600000000000 1458977 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": 998535, "vin": [ { "gen": { "height": 998525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4563ec860f02fe7c9079f889e840a82feb57a9af8fbc4bdb997e050d7d3f294" } } ], "extra": [ 1, 140, 37, 230, 91, 109, 147, 17, 243, 140, 173, 198, 7, 167, 47, 67, 66, 1, 153, 182, 114, 89, 15, 129, 234, 233, 108, 127, 75, 144, 231, 201, 7, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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