Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2520b583a4c077074bb089746d38ef12d24840363bfd1d8bc7be736edba66459

Tx prefix hash: e0deecef545d76d54bf1090a72f3cb6d349081cf8009128136a165cca9143c76
Tx public key: 8bb7e88452fa71ee7b864a95226666c31b6604a59d5c39b2d192f33dfb330fdf
Timestamp: 1733258702 Timestamp [UCT]: 2024-12-03 20:45:02 Age [y:d:h:m:s]: 00:028:23:56:22
Block: 1167373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20736 RingCT/type: yes/0
Extra: 018bb7e88452fa71ee7b864a95226666c31b6604a59d5c39b2d192f33dfb330fdf021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d3ab330cb1e4c1ac83c065f62a88c894e3e5ac112b3ab0c31a3cd0ebf4c3f8f 0.600000000000 1653068 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": 1167383, "vin": [ { "gen": { "height": 1167373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d3ab330cb1e4c1ac83c065f62a88c894e3e5ac112b3ab0c31a3cd0ebf4c3f8f" } } ], "extra": [ 1, 139, 183, 232, 132, 82, 250, 113, 238, 123, 134, 74, 149, 34, 102, 102, 195, 27, 102, 4, 165, 157, 92, 57, 178, 209, 146, 243, 61, 251, 51, 15, 223, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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