Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832d8686529cfbf8ac6a67c611e90a4fd84f92228a4379e59403426f0805e9ec

Tx prefix hash: ae23b60579b92028a72c9b3dc0e58bdc7481c46a8b598d96497f39f311f70ad0
Tx public key: 35e412b82b388f1ea29b8a614c8718a06db258798dc2baad1379d1442986bde4
Timestamp: 1707651324 Timestamp [UCT]: 2024-02-11 11:35:24 Age [y:d:h:m:s]: 01:051:20:50:24
Block: 955170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298112 RingCT/type: yes/0
Extra: 0135e412b82b388f1ea29b8a614c8718a06db258798dc2baad1379d1442986bde402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3eaded373fa5bce78fd957244ba2d2fafc1018bb4f0352df9d016ed1cc7ac1dc 0.600000000000 1414456 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": 955180, "vin": [ { "gen": { "height": 955170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3eaded373fa5bce78fd957244ba2d2fafc1018bb4f0352df9d016ed1cc7ac1dc" } } ], "extra": [ 1, 53, 228, 18, 184, 43, 56, 143, 30, 162, 155, 138, 97, 76, 135, 24, 160, 109, 178, 88, 121, 141, 194, 186, 173, 19, 121, 209, 68, 41, 134, 189, 228, 2, 17, 0, 0, 0, 4, 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