Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4490480649b7428c78b7d45bddc3e272601b80b383a44962c978b80a252c804e

Tx prefix hash: f33d936f404840f6dbe39bada4e9579dadabc1c3bb646fe3c85ce726a822b5f5
Tx public key: a88b38090225f65f10c384bb5e2bdacd935f048f78d0aee64cd77e6a7e94b8d1
Timestamp: 1720141435 Timestamp [UCT]: 2024-07-05 01:03:55 Age [y:d:h:m:s]: 00:320:20:09:06
Block: 1058716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229303 RingCT/type: yes/0
Extra: 01a88b38090225f65f10c384bb5e2bdacd935f048f78d0aee64cd77e6a7e94b8d102110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60e0285f05bb8cade1495d58a1b33445230efe99c3e8fcf9da3c68fa19b71823 0.600000000000 1529173 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": 1058726, "vin": [ { "gen": { "height": 1058716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60e0285f05bb8cade1495d58a1b33445230efe99c3e8fcf9da3c68fa19b71823" } } ], "extra": [ 1, 168, 139, 56, 9, 2, 37, 246, 95, 16, 195, 132, 187, 94, 43, 218, 205, 147, 95, 4, 143, 120, 208, 174, 230, 76, 215, 126, 106, 126, 148, 184, 209, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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