Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26c347c95bc2b54fcf703e792c067a3da2df385e9676e0fc077fa4f40805e7d4

Tx prefix hash: 0dcd3f0502d21f47d969293e28a77adf464b7f85eb6cbdc09d5a0695da252fc8
Tx public key: f8358b2632ecd2e41a43a2d0a0bce961e1d810731f8bc52ef1154e5f87e98da5
Timestamp: 1738582527 Timestamp [UCT]: 2025-02-03 11:35:27 Age [y:d:h:m:s]: 00:357:18:46:40
Block: 1211176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253389 RingCT/type: yes/0
Extra: 01f8358b2632ecd2e41a43a2d0a0bce961e1d810731f8bc52ef1154e5f87e98da50211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0f3f70c603f8e0e09c302fa99653db19e3591178bb673431ac4df376d25a5ea 0.600000000000 1697935 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": 1211186, "vin": [ { "gen": { "height": 1211176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0f3f70c603f8e0e09c302fa99653db19e3591178bb673431ac4df376d25a5ea" } } ], "extra": [ 1, 248, 53, 139, 38, 50, 236, 210, 228, 26, 67, 162, 208, 160, 188, 233, 97, 225, 216, 16, 115, 31, 139, 197, 46, 241, 21, 78, 95, 135, 233, 141, 165, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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