Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82f9be2abf5896986dca650421b68dc570560482c059b0a251361ac8de91c29d

Tx prefix hash: 0dea0e694754e45957557d0c29b6c30e8940dde6f0f07b5fcfe540e4d343d4f9
Tx public key: 690c2e5dd82737fed09a4f17c131615d261538cda3e51368dbb169a2f9049da4
Timestamp: 1723193452 Timestamp [UCT]: 2024-08-09 08:50:52 Age [y:d:h:m:s]: 00:237:14:34:31
Block: 1084029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169704 RingCT/type: yes/0
Extra: 01690c2e5dd82737fed09a4f17c131615d261538cda3e51368dbb169a2f9049da402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8c6366a5abbe3e4d94bc2518a6387a3ec126a5de5df44410c7b0ae9aa9ea7ad 0.600000000000 1558158 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": 1084039, "vin": [ { "gen": { "height": 1084029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8c6366a5abbe3e4d94bc2518a6387a3ec126a5de5df44410c7b0ae9aa9ea7ad" } } ], "extra": [ 1, 105, 12, 46, 93, 216, 39, 55, 254, 208, 154, 79, 23, 193, 49, 97, 93, 38, 21, 56, 205, 163, 229, 19, 104, 219, 177, 105, 162, 249, 4, 157, 164, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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