Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 058084dd26651130690bd0522b9efb068a68fbefb304362cab840926dbbcfffd

Tx prefix hash: 9519e50cb0337de51588c45e31d82d1e79eb02e57b3280770d2bdf47ff534f79
Tx public key: 6a191a1dcd5f2d34565768a8d5dbe137854a1f6bbae6f73ec0aa2197345de20d
Timestamp: 1764524254 Timestamp [UTC]: 2025-11-30 17:37:34 Age [y:d:h:m:s]: 00:167:14:13:21
Block: 1423561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112157 RingCT/type: yes/0
Extra: 016a191a1dcd5f2d34565768a8d5dbe137854a1f6bbae6f73ec0aa2197345de20d0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 093b6e348ac50a72baa5d447fb31f55dd0dc29b46570ea71bb406d8cf96e2f24 0.000600000000 1912174 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": 1423571, "vin": [ { "gen": { "height": 1423561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "093b6e348ac50a72baa5d447fb31f55dd0dc29b46570ea71bb406d8cf96e2f24" } } ], "extra": [ 1, 106, 25, 26, 29, 205, 95, 45, 52, 86, 87, 104, 168, 213, 219, 225, 55, 133, 74, 31, 107, 186, 230, 247, 62, 192, 170, 33, 151, 52, 93, 226, 13, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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: