Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51151cae17cc52bd95319b98fb6ffa20c79bbb66cefae24090cd028d9b05a69c

Tx prefix hash: 17e39c978f7656f1fa1beb64f9bdfcea6362d6930f5700180a0a20beb7179aa9
Tx public key: 8e7847d97f8929b8f6f24581b830aca922fbb6165d6834fe62cb2a739515dea0
Timestamp: 1737705075 Timestamp [UCT]: 2025-01-24 07:51:15 Age [y:d:h:m:s]: 01:004:15:07:59
Block: 1204145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261635 RingCT/type: yes/0
Extra: 018e7847d97f8929b8f6f24581b830aca922fbb6165d6834fe62cb2a739515dea00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ec85a15b9e6af905b6ddb3175a76be86ec2fe65f3c91859a86b22a04a8d0e77 0.600000000000 1690828 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": 1204155, "vin": [ { "gen": { "height": 1204145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ec85a15b9e6af905b6ddb3175a76be86ec2fe65f3c91859a86b22a04a8d0e77" } } ], "extra": [ 1, 142, 120, 71, 217, 127, 137, 41, 184, 246, 242, 69, 129, 184, 48, 172, 169, 34, 251, 182, 22, 93, 104, 52, 254, 98, 203, 42, 115, 149, 21, 222, 160, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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