Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4542fa0559a508d4eac55d08d661942b24c062e7e5bf4a549e263abd2bf02c14

Tx prefix hash: b2f8acf9b90eaee1e42598d9049d834ebc0f40c4568f60c9f370e003f6e93cf9
Tx public key: d81230b4101dd3f61cb1ef2f45072f05c61903a9d82d0204e07610a188df0988
Timestamp: 1752379014 Timestamp [UTC]: 2025-07-13 03:56:54 Age [y:d:h:m:s]: 01:124:07:45:50
Block: 1324348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353766 RingCT/type: yes/0
Extra: 01d81230b4101dd3f61cb1ef2f45072f05c61903a9d82d0204e07610a188df09880211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d9d72e2441d9e24a31fb455208158f96f44ef0c19aaf83a4f82c12fc749f4511 0.000600000000 1812091 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": 1324358, "vin": [ { "gen": { "height": 1324348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9d72e2441d9e24a31fb455208158f96f44ef0c19aaf83a4f82c12fc749f4511" } } ], "extra": [ 1, 216, 18, 48, 180, 16, 29, 211, 246, 28, 177, 239, 47, 69, 7, 47, 5, 198, 25, 3, 169, 216, 45, 2, 4, 224, 118, 16, 161, 136, 223, 9, 136, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: