Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d366a5b07bcc7191ea6a4165087373836e854a7bb57366523aa88a235544949

Tx prefix hash: 228e1441222ccca63f36711375f111513b6fcd520eff7a7ec8a1c7db88b3ade1
Tx public key: e333b269e8af3702f0c6d5df44b0bedfe3d9daf4b89418aaca7f1303cf4b1b83
Timestamp: 1734503256 Timestamp [UCT]: 2024-12-18 06:27:36 Age [y:d:h:m:s]: 00:127:13:16:49
Block: 1177713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90933 RingCT/type: yes/0
Extra: 01e333b269e8af3702f0c6d5df44b0bedfe3d9daf4b89418aaca7f1303cf4b1b830211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83674a0913a043c226bfe2b58671e6c62ada63610c7a468a05887744cbc76ec9 0.600000000000 1664088 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": 1177723, "vin": [ { "gen": { "height": 1177713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83674a0913a043c226bfe2b58671e6c62ada63610c7a468a05887744cbc76ec9" } } ], "extra": [ 1, 227, 51, 178, 105, 232, 175, 55, 2, 240, 198, 213, 223, 68, 176, 190, 223, 227, 217, 218, 244, 184, 148, 24, 170, 202, 127, 19, 3, 207, 75, 27, 131, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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