Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344a4193652dcf69c9eb8d5ecba12c8986ed1cb33900f906626f6c07ea04daa4

Tx prefix hash: 322611e670c7331d9ca00adf5cc6d66591f2ab0ab75b6733663f75cc60f819a2
Tx public key: a84e559c6dad8f1b7bc653d54b3454a70d20d4bc04dc578fbc2409557437c25e
Timestamp: 1750308971 Timestamp [UTC]: 2025-06-19 04:56:11 Age [y:d:h:m:s]: 00:326:14:34:06
Block: 1308124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223414 RingCT/type: yes/0
Extra: 01a84e559c6dad8f1b7bc653d54b3454a70d20d4bc04dc578fbc2409557437c25e021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b91c17a0dfb79161ac1ccf02a57f690b8c3d5a027593a408ece62451a41ab065 0.000600000000 1795737 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": 1308134, "vin": [ { "gen": { "height": 1308124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b91c17a0dfb79161ac1ccf02a57f690b8c3d5a027593a408ece62451a41ab065" } } ], "extra": [ 1, 168, 78, 85, 156, 109, 173, 143, 27, 123, 198, 83, 213, 75, 52, 84, 167, 13, 32, 212, 188, 4, 220, 87, 143, 188, 36, 9, 85, 116, 55, 194, 94, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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: