Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe5ae5e44556d5bf87d449b269f552f7cb9e51f7d3c15aa88756aafa077f17bc

Tx prefix hash: b68a0e7434fde89a33108b1f0fc576f53cca792fdca36dea6b6d823310feec7f
Tx public key: ef616749c3382a5eb8cbe527c7701e967b923090cb037229b5582cf95b5e9528
Timestamp: 1736798853 Timestamp [UCT]: 2025-01-13 20:07:33 Age [y:d:h:m:s]: 00:309:18:05:01
Block: 1196678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218893 RingCT/type: yes/0
Extra: 01ef616749c3382a5eb8cbe527c7701e967b923090cb037229b5582cf95b5e95280211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d125d52febdb5116045c45fa68f3dfd9516b1aea57593c831033ffd82515dff 0.600000000000 1683279 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": 1196688, "vin": [ { "gen": { "height": 1196678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d125d52febdb5116045c45fa68f3dfd9516b1aea57593c831033ffd82515dff" } } ], "extra": [ 1, 239, 97, 103, 73, 195, 56, 42, 94, 184, 203, 229, 39, 199, 112, 30, 150, 123, 146, 48, 144, 203, 3, 114, 41, 181, 88, 44, 249, 91, 94, 149, 40, 2, 17, 0, 0, 0, 2, 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