Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd552bc05e8bd04dee18eb175c0196aa4e98f8eddce3875c3f9f5c1bda149221

Tx prefix hash: ea44b1814c0df0f4c8e7949251d92d3b775f85eba9bb735b3e3a142bd272b277
Tx public key: 1a7d6f71701a056d700d2e7b96cb0aabbd18ff8dc5f39797d463075f7aa7657b
Timestamp: 1718554563 Timestamp [UCT]: 2024-06-16 16:16:03 Age [y:d:h:m:s]: 00:288:08:45:36
Block: 1045589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206043 RingCT/type: yes/0
Extra: 011a7d6f71701a056d700d2e7b96cb0aabbd18ff8dc5f39797d463075f7aa7657b02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e412170d96401d8a3fec31fe8937c1c35bb173f91adb3a4abfa852d51f957f7 0.600000000000 1515200 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": 1045599, "vin": [ { "gen": { "height": 1045589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e412170d96401d8a3fec31fe8937c1c35bb173f91adb3a4abfa852d51f957f7" } } ], "extra": [ 1, 26, 125, 111, 113, 112, 26, 5, 109, 112, 13, 46, 123, 150, 203, 10, 171, 189, 24, 255, 141, 197, 243, 151, 151, 212, 99, 7, 95, 122, 167, 101, 123, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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