Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c1c9598194dc86c3271f64b961ff9d535bc1fba23c22384b6107f12a4dc814b

Tx prefix hash: 5dbe90bf2640a529c7a93e3acc38c9a98b3efd88d5edacea48a2fc9127fefa83
Tx public key: fed802c535fbd9e9412cc087c1832e5e6fa999b464bedb9cd4cb74c80842fffb
Timestamp: 1736731137 Timestamp [UCT]: 2025-01-13 01:18:57 Age [y:d:h:m:s]: 00:342:14:29:39
Block: 1196117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242423 RingCT/type: yes/0
Extra: 01fed802c535fbd9e9412cc087c1832e5e6fa999b464bedb9cd4cb74c80842fffb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a50996015899c8a84c55fe943e382a41a47161e296f832e107126aa1388da1a3 0.600000000000 1682714 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": 1196127, "vin": [ { "gen": { "height": 1196117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a50996015899c8a84c55fe943e382a41a47161e296f832e107126aa1388da1a3" } } ], "extra": [ 1, 254, 216, 2, 197, 53, 251, 217, 233, 65, 44, 192, 135, 193, 131, 46, 94, 111, 169, 153, 180, 100, 190, 219, 156, 212, 203, 116, 200, 8, 66, 255, 251, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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