Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53d0439c0df4d04da47c31fe7230ecb5b6908154eba9f662c8c664921e87fe92

Tx prefix hash: 526499972d6b343c07e4723897b368d18931c6fd182774085414f9213b487581
Tx public key: a859ec9ca5d731ecf6804db56039e500da8a41d8e45f03ce4555fa516d3c2cc3
Timestamp: 1773835134 Timestamp [UTC]: 2026-03-18 11:58:54 Age [y:d:h:m:s]: 00:249:05:06:29
Block: 1500471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183023 RingCT/type: yes/0
Extra: 01a859ec9ca5d731ecf6804db56039e500da8a41d8e45f03ce4555fa516d3c2cc3021100000010f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5d004fe87a0ea444e0e3f34f9412c57bbf21e382bac5354b8ea2a94e0357e740 0.000600000000 1990143 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": 1500481, "vin": [ { "gen": { "height": 1500471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d004fe87a0ea444e0e3f34f9412c57bbf21e382bac5354b8ea2a94e0357e740" } } ], "extra": [ 1, 168, 89, 236, 156, 165, 215, 49, 236, 246, 128, 77, 181, 96, 57, 229, 0, 218, 138, 65, 216, 228, 95, 3, 206, 69, 85, 250, 81, 109, 60, 44, 195, 2, 17, 0, 0, 0, 16, 241, 136, 200, 168, 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: