Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3c540ea9c301ebd4f0ae8abb5a93f4f7d2646b4ed8c7e9e3927002fcc19c7a0

Tx prefix hash: eb266db89aa4565c9451de1dc4a1f1246611d279ad8cf9e13595b31d8914c64a
Tx public key: f5476115d11a135f5a80cc86115c94e9544459b68e9f0b4cb3861fe23bef1674
Timestamp: 1765739342 Timestamp [UTC]: 2025-12-14 19:09:02 Age [y:d:h:m:s]: 00:153:19:14:51
Block: 1433615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102324 RingCT/type: yes/0
Extra: 01f5476115d11a135f5a80cc86115c94e9544459b68e9f0b4cb3861fe23bef16740211000000017b1e51ac000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 229e4ea41eb0f32cd057d13b6211cdd9aa58936657b73f92ef58705fcd65ca5d 0.000600000000 1922396 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": 1433625, "vin": [ { "gen": { "height": 1433615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "229e4ea41eb0f32cd057d13b6211cdd9aa58936657b73f92ef58705fcd65ca5d" } } ], "extra": [ 1, 245, 71, 97, 21, 209, 26, 19, 95, 90, 128, 204, 134, 17, 92, 148, 233, 84, 68, 89, 182, 142, 159, 11, 76, 179, 134, 31, 226, 59, 239, 22, 116, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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: