Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a346161ae9c415cc1366552555d150891491af950982c1b62d5603dbf0f07dc

Tx prefix hash: 91cf156d5f78b541c3ed9680181118c28b0dadf05214a372073453d7bea57e3b
Tx public key: 4de9c3656667b5fa974a7cd65cb5aedbd362d2d7df4049aa12ac4ba2bb82fc46
Timestamp: 1603727580 Timestamp [UTC]: 2020-10-26 15:53:00 Age [y:d:h:m:s]: 05:332:18:53:32
Block: 144301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1497454 RingCT/type: yes/0
Extra: 014de9c3656667b5fa974a7cd65cb5aedbd362d2d7df4049aa12ac4ba2bb82fc46021100000017f4b4cc44000000000000000000

1 output(s) for total of 0.204136251431 xmr

stealth address amount amount idx tag
00: ded97e94db7f980cb60ea3c4f188cc9aa80ed9eeb04ff6e76c01e0e827d2ff65 0.204136251431 239811 of 0 -

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 dinastycoin-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": 144311, "vin": [ { "gen": { "height": 144301 } } ], "vout": [ { "amount": 204136251431, "target": { "key": "ded97e94db7f980cb60ea3c4f188cc9aa80ed9eeb04ff6e76c01e0e827d2ff65" } } ], "extra": [ 1, 77, 233, 195, 101, 102, 103, 181, 250, 151, 74, 124, 214, 92, 181, 174, 219, 211, 98, 210, 215, 223, 64, 73, 170, 18, 172, 75, 162, 187, 130, 252, 70, 2, 17, 0, 0, 0, 23, 244, 180, 204, 68, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: