Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99f20ec17d1910fce5adf9c47e089ed824017389de2ffbe4ec5037e30af76d9c

Tx prefix hash: 637113b65d735f572aa6548d795c7fccbee3b52a23be509ac711659c975b09f0
Tx public key: 7cc5da2676585b169827f815fbd1fefd9eabc0a693a4a2d8be9a9da6675afcd4
Timestamp: 1720299563 Timestamp [UCT]: 2024-07-06 20:59:23 Age [y:d:h:m:s]: 00:111:14:22:08
Block: 1060030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79918 RingCT/type: yes/0
Extra: 017cc5da2676585b169827f815fbd1fefd9eabc0a693a4a2d8be9a9da6675afcd402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46964ff8940532218292d89d310d78dd0c5b408b60c144db09594d647cf036b6 0.600000000000 1530501 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": 1060040, "vin": [ { "gen": { "height": 1060030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46964ff8940532218292d89d310d78dd0c5b408b60c144db09594d647cf036b6" } } ], "extra": [ 1, 124, 197, 218, 38, 118, 88, 91, 22, 152, 39, 248, 21, 251, 209, 254, 253, 158, 171, 192, 166, 147, 164, 162, 216, 190, 154, 157, 166, 103, 90, 252, 212, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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