Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b142dae4ca314edca44cc38eb87e6e8769969a3e16f0da563b33691b5fe74972

Tx prefix hash: 076736d2cd2c39d994a9477f8ca12b59976bdb2ea43768eead054e5647c13f5c
Tx public key: 126803577a0d4a0dfcd9b4094971e0c4ffe567be58b8f4ca9c2623a3cc27209d
Timestamp: 1754383565 Timestamp [UCT]: 2025-08-05 08:46:05 Age [y:d:h:m:s]: 00:054:10:18:22
Block: 1340679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37799 RingCT/type: yes/0
Extra: 01126803577a0d4a0dfcd9b4094971e0c4ffe567be58b8f4ca9c2623a3cc27209d021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18c8913acc907f21baf96b72d7b882c0d413f0b12121894b11a996bf539f3deb 0.600000000000 1828498 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": 1340689, "vin": [ { "gen": { "height": 1340679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18c8913acc907f21baf96b72d7b882c0d413f0b12121894b11a996bf539f3deb" } } ], "extra": [ 1, 18, 104, 3, 87, 122, 13, 74, 13, 252, 217, 180, 9, 73, 113, 224, 196, 255, 229, 103, 190, 88, 184, 244, 202, 156, 38, 35, 163, 204, 39, 32, 157, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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