Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b1ff0c78562b1ce5c1b655757ec9cd18eb7e0fdd08c8c9a114102014ec042f

Tx prefix hash: e267d67c83f4a6beda924ac713e4784663ad08d08035ebb22a2bdb2377f288a4
Tx public key: d351e2cc8459c4e53f0987db2d23a499017484b2aab47375da2bddcd23f253c4
Timestamp: 1759760196 Timestamp [UTC]: 2025-10-06 14:16:36 Age [y:d:h:m:s]: 00:217:07:35:27
Block: 1384075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147554 RingCT/type: yes/0
Extra: 01d351e2cc8459c4e53f0987db2d23a499017484b2aab47375da2bddcd23f253c4021100000007dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b1d8bd7c85c4ccc340562e884a6afd47ea29a9b56b028b0d4ada44811650057f 0.000600000000 1872224 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 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": 1384085, "vin": [ { "gen": { "height": 1384075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1d8bd7c85c4ccc340562e884a6afd47ea29a9b56b028b0d4ada44811650057f" } } ], "extra": [ 1, 211, 81, 226, 204, 132, 89, 196, 229, 63, 9, 135, 219, 45, 35, 164, 153, 1, 116, 132, 178, 170, 180, 115, 117, 218, 43, 221, 205, 35, 242, 83, 196, 2, 17, 0, 0, 0, 7, 223, 195, 186, 73, 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: