Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1336dc137ea2bf229cd9171717e61e76e4c2c078f82643eda17b28f2b78fbca

Tx prefix hash: 4a3c78f2e65588fb241c928b82a861c48f122b1246d5e448d84e587f70b4deed
Tx public key: 2a1f19960525ed04852ef8a650d7dc9c390e9cb47e46262595538b90c74b6049
Timestamp: 1773178566 Timestamp [UTC]: 2026-03-10 21:36:06 Age [y:d:h:m:s]: 00:255:00:44:17
Block: 1495056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187919 RingCT/type: yes/0
Extra: 012a1f19960525ed04852ef8a650d7dc9c390e9cb47e46262595538b90c74b6049021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8e182b7453f7f6a0ef92c831b4bc133822b6b406c5a63e3c27e7f5e7fe5e62e6 0.000600000000 1984664 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": 1495066, "vin": [ { "gen": { "height": 1495056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e182b7453f7f6a0ef92c831b4bc133822b6b406c5a63e3c27e7f5e7fe5e62e6" } } ], "extra": [ 1, 42, 31, 25, 150, 5, 37, 237, 4, 133, 46, 248, 166, 80, 215, 220, 156, 57, 14, 156, 180, 126, 70, 38, 37, 149, 83, 139, 144, 199, 75, 96, 73, 2, 17, 0, 0, 0, 7, 228, 245, 25, 63, 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: