Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f11328de4ee17304a1b8025a60a072d13c4b725fa663141925e1950bd1cc7805

Tx prefix hash: 39c00ef7f769bfd21c695572cc79e0df367688ba60a241733ded4ca4f3360ef0
Tx public key: a35c6595e9ef1d0d4e7d4b5b71e92665bdc67689ae4617a22b53edce6919c5ef
Timestamp: 1715555938 Timestamp [UCT]: 2024-05-12 23:18:58 Age [y:d:h:m:s]: 00:324:09:44:47
Block: 1020739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231843 RingCT/type: yes/0
Extra: 01a35c6595e9ef1d0d4e7d4b5b71e92665bdc67689ae4617a22b53edce6919c5ef0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 264610592d5c3406a089dc9b64b539dca1e4a879f0c83f2231e012be135a06a0 0.600000000000 1484820 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": 1020749, "vin": [ { "gen": { "height": 1020739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "264610592d5c3406a089dc9b64b539dca1e4a879f0c83f2231e012be135a06a0" } } ], "extra": [ 1, 163, 92, 101, 149, 233, 239, 29, 13, 78, 125, 75, 91, 113, 233, 38, 101, 189, 198, 118, 137, 174, 70, 23, 162, 43, 83, 237, 206, 105, 25, 197, 239, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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