Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a603720a9c74bf93682556ad75b6eed23c913c3198c03921db064081a9b92d4

Tx prefix hash: 3bf2588899ccad5bd3cdabf55348f5a44b740477b340563015f7096dbfb3b156
Tx public key: 8ac478a72814570a9c47bc2fbc3d1402051269d699cc904f7eb8cca989b6b99e
Timestamp: 1696213788 Timestamp [UCT]: 2023-10-02 02:29:48 Age [y:d:h:m:s]: 01:147:09:27:13
Block: 860564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366352 RingCT/type: yes/0
Extra: 018ac478a72814570a9c47bc2fbc3d1402051269d699cc904f7eb8cca989b6b99e02110000001275e3f0e9000000000000000000

1 output(s) for total of 0.864160223000 dcy

stealth address amount amount idx
00: c84f3dee31547e5e7f57d525658264fbe3a10b2d364ef9989cf2a1e2f4eae32b 0.864160223000 1314854 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": 860574, "vin": [ { "gen": { "height": 860564 } } ], "vout": [ { "amount": 864160223, "target": { "key": "c84f3dee31547e5e7f57d525658264fbe3a10b2d364ef9989cf2a1e2f4eae32b" } } ], "extra": [ 1, 138, 196, 120, 167, 40, 20, 87, 10, 156, 71, 188, 47, 188, 61, 20, 2, 5, 18, 105, 214, 153, 204, 144, 79, 126, 184, 204, 169, 137, 182, 185, 158, 2, 17, 0, 0, 0, 18, 117, 227, 240, 233, 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