Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b82c873750d192883e808bb5df5eb798c0449e8cb3183c53dd79768f2f951ac

Tx prefix hash: dc6bf1f4bba796810d75a35d37c6cec2b3b965d8d699c2bbe70491d7bba8cead
Tx public key: 42d7a0858eaba2c3ea0a321d32fe4f0a2a55e5c0f8aaeddd66a375b94653fb52
Timestamp: 1747197616 Timestamp [UTC]: 2025-05-14 04:40:16 Age [y:d:h:m:s]: 01:103:01:01:12
Block: 1282508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337968 RingCT/type: yes/0
Extra: 0142d7a0858eaba2c3ea0a321d32fe4f0a2a55e5c0f8aaeddd66a375b94653fb520211000000059f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 02002424a71ba5f4a8b2474c46a21b8318a67b7644f0ab9710e03ff3c459d2ab 0.000600000000 1769915 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": 1282518, "vin": [ { "gen": { "height": 1282508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02002424a71ba5f4a8b2474c46a21b8318a67b7644f0ab9710e03ff3c459d2ab" } } ], "extra": [ 1, 66, 215, 160, 133, 142, 171, 162, 195, 234, 10, 50, 29, 50, 254, 79, 10, 42, 85, 229, 192, 248, 170, 237, 221, 102, 163, 117, 185, 70, 83, 251, 82, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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: