Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4c22e2568900c4f803acc1678981c6dc0331d26e28c747f8b5855049cfda78f

Tx prefix hash: 0d049d5a9adcda795c8305f922264b38812439bae14898dfec5b8b909d9e5f8e
Tx public key: a0ceb30076225ff5a9190c12c371c0ba816c7ca11129a84320814f9a984f71f2
Timestamp: 1727688503 Timestamp [UCT]: 2024-09-30 09:28:23 Age [y:d:h:m:s]: 00:139:06:30:37
Block: 1121301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99279 RingCT/type: yes/0
Extra: 01a0ceb30076225ff5a9190c12c371c0ba816c7ca11129a84320814f9a984f71f2021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df1f9c154fbfb849064b8b0deb320576fffec346dca267a34b13bb0d2e7d0f0e 0.600000000000 1603524 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": 1121311, "vin": [ { "gen": { "height": 1121301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df1f9c154fbfb849064b8b0deb320576fffec346dca267a34b13bb0d2e7d0f0e" } } ], "extra": [ 1, 160, 206, 179, 0, 118, 34, 95, 245, 169, 25, 12, 18, 195, 113, 192, 186, 129, 108, 124, 161, 17, 41, 168, 67, 32, 129, 79, 154, 152, 79, 113, 242, 2, 17, 0, 0, 0, 5, 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