Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b58cfca03bff96f354b17828a10f3673c8a1be26cfe87c416309ae75eabf4a9

Tx prefix hash: 8ef024aa76d324f01e715d1d5b5d4e6d30ea3bb5828b32273727a1e07a973cd8
Tx public key: acd015e9b2fa8023849c4f74c9b252c69f3b639719272ee19e71578a209564fc
Timestamp: 1773824352 Timestamp [UTC]: 2026-03-18 08:59:12 Age [y:d:h:m:s]: 00:054:07:15:56
Block: 1500378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31151 RingCT/type: yes/0
Extra: 01acd015e9b2fa8023849c4f74c9b252c69f3b639719272ee19e71578a209564fc021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 36cf1b7dd1503deb3f12b62b5b30d93161230cdfef69c2c389ce5b6d16cc1022 0.000600000000 1990050 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": 1500388, "vin": [ { "gen": { "height": 1500378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36cf1b7dd1503deb3f12b62b5b30d93161230cdfef69c2c389ce5b6d16cc1022" } } ], "extra": [ 1, 172, 208, 21, 233, 178, 250, 128, 35, 132, 156, 79, 116, 201, 178, 82, 198, 159, 59, 99, 151, 25, 39, 46, 225, 158, 113, 87, 138, 32, 149, 100, 252, 2, 17, 0, 0, 0, 1, 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: