Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d9f3b319e9c6a949e6aa68a817348fc3c721bc3b4cd6865fa8ead46933a9b2b

Tx prefix hash: 506ad3dfd8aade73dd8d9fdf1c6c9cd249dbc77836440e9b778ee2cdc95d85c9
Tx public key: b08334ab46103e6876f4da407914517a1c7ea82a91a8ffc0f0e6025767da9257
Timestamp: 1708881385 Timestamp [UTC]: 2024-02-25 17:16:25 Age [y:d:h:m:s]: 02:080:01:21:16
Block: 965386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569156 RingCT/type: yes/0
Extra: 01b08334ab46103e6876f4da407914517a1c7ea82a91a8ffc0f0e6025767da92570211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0b9d68c7c2c5efe10f1acaa2a4c4fcbbea1a0aeccd17bb79472e3fe7504b67d2 0.000600000000 1425137 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": 965396, "vin": [ { "gen": { "height": 965386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b9d68c7c2c5efe10f1acaa2a4c4fcbbea1a0aeccd17bb79472e3fe7504b67d2" } } ], "extra": [ 1, 176, 131, 52, 171, 70, 16, 62, 104, 118, 244, 218, 64, 121, 20, 81, 122, 28, 126, 168, 42, 145, 168, 255, 192, 240, 230, 2, 87, 103, 218, 146, 87, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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: