Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa17d5b211312c7a89ff6951d6aab247edd5839e30824f14aefa20bec6981c3f

Tx prefix hash: ee3747a583b8998e7b961e3d8a0c7ccbab7334fb64de54ae7fec621fb839c7fc
Tx public key: 388dd1e77f2086fd9eb576078cb0f32734f66bf2f43a1753080f2817fcec216a
Timestamp: 1707038110 Timestamp [UCT]: 2024-02-04 09:15:10 Age [y:d:h:m:s]: 01:002:08:57:21
Block: 950088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262722 RingCT/type: yes/0
Extra: 01388dd1e77f2086fd9eb576078cb0f32734f66bf2f43a1753080f2817fcec216a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0eb1f4c070a1928068a2f8985bc7140e37ec5d096cfb234f1f27934f3f79c3a 0.600000000000 1408648 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": 950098, "vin": [ { "gen": { "height": 950088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0eb1f4c070a1928068a2f8985bc7140e37ec5d096cfb234f1f27934f3f79c3a" } } ], "extra": [ 1, 56, 141, 209, 231, 127, 32, 134, 253, 158, 181, 118, 7, 140, 176, 243, 39, 52, 246, 107, 242, 244, 58, 23, 83, 8, 15, 40, 23, 252, 236, 33, 106, 2, 17, 0, 0, 0, 2, 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