Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17a7f373e4b7bf3071e267b1861e403edece19f31456f8e5795561df4a0b1918

Tx prefix hash: d57e69d4b818f4948a77b9c606c7c54a625cfd1dc29cfd1f973cf80c52797cc5
Tx public key: baf86d3d8054aec43984afbe35edbca25af6c095406e6b660265b4676cc8493b
Timestamp: 1659605528 Timestamp [UCT]: 2022-08-04 09:32:08 Age [y:d:h:m:s]: 02:229:20:53:35
Block: 558436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 685507 RingCT/type: yes/0
Extra: 01baf86d3d8054aec43984afbe35edbca25af6c095406e6b660265b4676cc8493b0211000000016570b1ef000000000000000000

1 output(s) for total of 8.663030314000 dcy

stealth address amount amount idx
00: 4f2e97800ad0a4c0846965ad90d99b5981a7b8c132efff68ed4def2e9f85fa0b 8.663030314000 990516 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": 558446, "vin": [ { "gen": { "height": 558436 } } ], "vout": [ { "amount": 8663030314, "target": { "key": "4f2e97800ad0a4c0846965ad90d99b5981a7b8c132efff68ed4def2e9f85fa0b" } } ], "extra": [ 1, 186, 248, 109, 61, 128, 84, 174, 196, 57, 132, 175, 190, 53, 237, 188, 162, 90, 246, 192, 149, 64, 110, 107, 102, 2, 101, 180, 103, 108, 200, 73, 59, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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