Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cf9c21f19595e7ef453d6d132198535f83605639de8dd04b8b4c9ab439d66f6

Tx prefix hash: d94f29c6f531a585e516e81a8b8e960419820e81e05b956b8f673be6c07fab4f
Tx public key: 9e5feda34d8b79c56ad3c55c80e528aa616592abbb119dff11ff2a808cdb51d3
Timestamp: 1737371144 Timestamp [UCT]: 2025-01-20 11:05:44 Age [y:d:h:m:s]: 00:148:13:55:11
Block: 1201371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105933 RingCT/type: yes/0
Extra: 019e5feda34d8b79c56ad3c55c80e528aa616592abbb119dff11ff2a808cdb51d3021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e4d629f662d41f8f5ff51aefef55092e930270920ad480e0b73d2ab899c7e82 0.600000000000 1688020 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": 1201381, "vin": [ { "gen": { "height": 1201371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e4d629f662d41f8f5ff51aefef55092e930270920ad480e0b73d2ab899c7e82" } } ], "extra": [ 1, 158, 95, 237, 163, 77, 139, 121, 197, 106, 211, 197, 92, 128, 229, 40, 170, 97, 101, 146, 171, 187, 17, 157, 255, 17, 255, 42, 128, 140, 219, 81, 211, 2, 17, 0, 0, 0, 4, 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