Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73661cf88d870ce06dda57a257311ef5a9a82b281a32c3ebc3de5f19ca697cb4

Tx prefix hash: 30b7c828e8a74d88c62a048ed15aaac609334e509aa7cbbad2ad3482c94a0ea0
Tx public key: 3e63563bfb3e47f3fef59711eb653e08d1ab3bf8f934a3f949015f4e86785f4b
Timestamp: 1725866783 Timestamp [UCT]: 2024-09-09 07:26:23 Age [y:d:h:m:s]: 00:261:14:37:10
Block: 1106199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186844 RingCT/type: yes/0
Extra: 013e63563bfb3e47f3fef59711eb653e08d1ab3bf8f934a3f949015f4e86785f4b02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d5e164a0e836148029f71aa3650f845807e95d254ebed92f677f320b5563504 0.600000000000 1583798 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": 1106209, "vin": [ { "gen": { "height": 1106199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d5e164a0e836148029f71aa3650f845807e95d254ebed92f677f320b5563504" } } ], "extra": [ 1, 62, 99, 86, 59, 251, 62, 71, 243, 254, 245, 151, 17, 235, 101, 62, 8, 209, 171, 59, 248, 249, 52, 163, 249, 73, 1, 95, 78, 134, 120, 95, 75, 2, 17, 0, 0, 0, 2, 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