Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c57b56633617bdba079cd1af425dcde4759a8195af543bf3e7fb9b327660639

Tx prefix hash: bc8b82ccd09e7d2bab8165fa53a256d2c160a2e2393d927d4b219ba5915a6120
Tx public key: 5351e3f31599cf58a6e4ef9591a55382cdb337be10c343b28a97772fce99d5c1
Timestamp: 1716698831 Timestamp [UCT]: 2024-05-26 04:47:11 Age [y:d:h:m:s]: 01:166:23:25:27
Block: 1030194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377917 RingCT/type: yes/0
Extra: 015351e3f31599cf58a6e4ef9591a55382cdb337be10c343b28a97772fce99d5c102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ef2674bc9f68a6b758d919609723a881c03003e2395b719e3b262c47834fb06 0.600000000000 1498447 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": 1030204, "vin": [ { "gen": { "height": 1030194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ef2674bc9f68a6b758d919609723a881c03003e2395b719e3b262c47834fb06" } } ], "extra": [ 1, 83, 81, 227, 243, 21, 153, 207, 88, 166, 228, 239, 149, 145, 165, 83, 130, 205, 179, 55, 190, 16, 195, 67, 178, 138, 151, 119, 47, 206, 153, 213, 193, 2, 17, 0, 0, 0, 3, 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