Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa3f10c30a8c025d4c3636d2e8664412d0a96df07ae9d12f636a9367b4d2740

Tx prefix hash: 99c42effcd36a0a768c55a352bcfe0db18eaf26033c0bbe918cf0a5041c3d824
Tx public key: 5a0747497ccb12904e683eba81d4c8dcdb40b07e506b61fb11910adf2690d33b
Timestamp: 1707743244 Timestamp [UCT]: 2024-02-12 13:07:24 Age [y:d:h:m:s]: 00:165:14:11:49
Block: 955940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118610 RingCT/type: yes/0
Extra: 015a0747497ccb12904e683eba81d4c8dcdb40b07e506b61fb11910adf2690d33b02110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43f001585d7590a9656e4159ad0ce030e4b152ad10f916b83e97140ae9f14b85 0.600000000000 1415240 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": 955950, "vin": [ { "gen": { "height": 955940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43f001585d7590a9656e4159ad0ce030e4b152ad10f916b83e97140ae9f14b85" } } ], "extra": [ 1, 90, 7, 71, 73, 124, 203, 18, 144, 78, 104, 62, 186, 129, 212, 200, 220, 219, 64, 176, 126, 80, 107, 97, 251, 17, 145, 10, 223, 38, 144, 211, 59, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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