Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c125bf644ad3c269bbcc095f3ea8f9d94125c2e509255c90132f3b186a328223

Tx prefix hash: e33c9b418231da79b6976d6077edce01041c2b1638b613035183eac0cc4e4d2f
Tx public key: 96be9a94291890bbd7a0f6c7d560ded4e09320b32419eab3801fe7687fb3aca2
Timestamp: 1739805917 Timestamp [UCT]: 2025-02-17 15:25:17 Age [y:d:h:m:s]: 00:271:07:58:12
Block: 1221291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191696 RingCT/type: yes/0
Extra: 0196be9a94291890bbd7a0f6c7d560ded4e09320b32419eab3801fe7687fb3aca20211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e319539df0209ad6f8c9b5f323c4c4a021b511e87657b35d45fd482780b57d06 0.600000000000 1708136 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": 1221301, "vin": [ { "gen": { "height": 1221291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e319539df0209ad6f8c9b5f323c4c4a021b511e87657b35d45fd482780b57d06" } } ], "extra": [ 1, 150, 190, 154, 148, 41, 24, 144, 187, 215, 160, 246, 199, 213, 96, 222, 212, 224, 147, 32, 179, 36, 25, 234, 179, 128, 31, 231, 104, 127, 179, 172, 162, 2, 17, 0, 0, 0, 7, 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