Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69f051c445185960c6b9aa24de6bad669ff78f7af67e3de863ce9e1a0f8b68dc

Tx prefix hash: 869704f98b89577d09b00bfd9aac129ae598457d5750abf1357aded71ff923f5
Tx public key: e37507e6cfc8f44df878d4c6e5f7ab5e326158c2e5824eca5493a39c732d0df3
Timestamp: 1709327772 Timestamp [UTC]: 2024-03-01 21:16:12 Age [y:d:h:m:s]: 02:265:13:31:10
Block: 969081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714413 RingCT/type: yes/0
Extra: 01e37507e6cfc8f44df878d4c6e5f7ab5e326158c2e5824eca5493a39c732d0df302110000000252d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b50eb9897a37f4dfbee717739bdb784e47878a518ccf3b6cc22b7d1c45bb4b60 0.000600000000 1428908 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": 969091, "vin": [ { "gen": { "height": 969081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b50eb9897a37f4dfbee717739bdb784e47878a518ccf3b6cc22b7d1c45bb4b60" } } ], "extra": [ 1, 227, 117, 7, 230, 207, 200, 244, 77, 248, 120, 212, 198, 229, 247, 171, 94, 50, 97, 88, 194, 229, 130, 78, 202, 84, 147, 163, 156, 115, 45, 13, 243, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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: