Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15d3d30e02e556fd5d6abc5a410e4802439dedb16f5944ebb7d62ac4ebc17486

Tx prefix hash: 604f9c1d935c539b1c5247d36c1a20f5f2a0297ac22beadf06176e4efa222ece
Tx public key: 89d64df32ba9f06b1b614c55ed655700241cef722269f784d346d3d050ce5526
Timestamp: 1712721742 Timestamp [UCT]: 2024-04-10 04:02:22 Age [y:d:h:m:s]: 00:364:19:23:27
Block: 997192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260829 RingCT/type: yes/0
Extra: 0189d64df32ba9f06b1b614c55ed655700241cef722269f784d346d3d050ce552602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e93ae0a23d1ccc3a04166715fd90e1adccacd0c9e24c68b3997c64fa3b17a23 0.600000000000 1457622 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": 997202, "vin": [ { "gen": { "height": 997192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e93ae0a23d1ccc3a04166715fd90e1adccacd0c9e24c68b3997c64fa3b17a23" } } ], "extra": [ 1, 137, 214, 77, 243, 43, 169, 240, 107, 27, 97, 76, 85, 237, 101, 87, 0, 36, 28, 239, 114, 34, 105, 247, 132, 211, 70, 211, 208, 80, 206, 85, 38, 2, 17, 0, 0, 0, 1, 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