Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44e47b8776f1c7b0c5a70c8903b227f945c430dd9e0e769f72184ead6f3fbaa

Tx prefix hash: d2aacb6f94ff064be83a8f77781b480c8eec13d0a93d22e9a7cfa52f1caad184
Tx public key: 6155a2455b83d005636cda1c851490c9bc5c66051624b253de1d08ad6ebc633f
Timestamp: 1749702581 Timestamp [UCT]: 2025-06-12 04:29:41 Age [y:d:h:m:s]: 00:162:07:31:57
Block: 1303209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113725 RingCT/type: yes/0
Extra: 016155a2455b83d005636cda1c851490c9bc5c66051624b253de1d08ad6ebc633f02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb2303dee290426c8eeaee447f378ac66ac35933c77e8d883043a0c3523a9144 0.600000000000 1790786 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": 1303219, "vin": [ { "gen": { "height": 1303209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb2303dee290426c8eeaee447f378ac66ac35933c77e8d883043a0c3523a9144" } } ], "extra": [ 1, 97, 85, 162, 69, 91, 131, 208, 5, 99, 108, 218, 28, 133, 20, 144, 201, 188, 92, 102, 5, 22, 36, 178, 83, 222, 29, 8, 173, 110, 188, 99, 63, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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