Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f0fe5cb52f3e71130e664109dc19163f3ebb40577edfa337ab8b58142936406

Tx prefix hash: ac69b6e4f968b70ee3846550a1a328a19cc3e7e0ccf5c8a30935a5bdfbd5a513
Tx public key: ab2496da0dfd1a6ba52f27c3677da37f934c675b020938e7f3be189a44115e65
Timestamp: 1724351381 Timestamp [UCT]: 2024-08-22 18:29:41 Age [y:d:h:m:s]: 00:230:03:35:19
Block: 1093641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164341 RingCT/type: yes/0
Extra: 01ab2496da0dfd1a6ba52f27c3677da37f934c675b020938e7f3be189a44115e6502110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ba388bce620536d3314b4d51ce0a0ba4d6c9730fa0c095bea3b686fdf550164 0.600000000000 1568626 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": 1093651, "vin": [ { "gen": { "height": 1093641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ba388bce620536d3314b4d51ce0a0ba4d6c9730fa0c095bea3b686fdf550164" } } ], "extra": [ 1, 171, 36, 150, 218, 13, 253, 26, 107, 165, 47, 39, 195, 103, 125, 163, 127, 147, 76, 103, 91, 2, 9, 56, 231, 243, 190, 24, 154, 68, 17, 94, 101, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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