Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2f12e6cc45030c6f764e1dc6f25db2fee446d1fa9acddd91b2f2e3e951eed0

Tx prefix hash: da2b1e4cea3b22fb2b8c8134fda69aa7be7be54ab68c823ebfc4d47a5eaed8be
Tx public key: a7742ca7105c0ab39763f43fc1bb5f2c7a34dd37c904890afd750855ce9b522e
Timestamp: 1699227429 Timestamp [UCT]: 2023-11-05 23:37:09 Age [y:d:h:m:s]: 01:086:23:52:38
Block: 885334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323345 RingCT/type: yes/0
Extra: 01a7742ca7105c0ab39763f43fc1bb5f2c7a34dd37c904890afd750855ce9b522e021100000001faf35c9c000000000000000000

1 output(s) for total of 0.715383890000 dcy

stealth address amount amount idx
00: ab98324c5ce5ddafb5b2e8e2f9b33cf7e6bb5a95cbd4920170316f65035159a3 0.715383890000 1341097 of 0

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": 885344, "vin": [ { "gen": { "height": 885334 } } ], "vout": [ { "amount": 715383890, "target": { "key": "ab98324c5ce5ddafb5b2e8e2f9b33cf7e6bb5a95cbd4920170316f65035159a3" } } ], "extra": [ 1, 167, 116, 44, 167, 16, 92, 10, 179, 151, 99, 244, 63, 193, 187, 95, 44, 122, 52, 221, 55, 201, 4, 137, 10, 253, 117, 8, 85, 206, 155, 82, 46, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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