Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 990e9ba239e50d6c77fe8982d13b7ea9e1aaa352cc7f89e66ea8f2a8a38a0f32

Tx prefix hash: 439e885f8016f94622a365be054eef2ad4dc16eff73443b71ef6b7f521ebb40c
Tx public key: ef519e04e1e25bf4d188374a5039631cb1032d0a973445bcdc5c90b53aff27ed
Timestamp: 1770842962 Timestamp [UTC]: 2026-02-11 20:49:22 Age [y:d:h:m:s]: 00:001:09:11:53
Block: 1475747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 989 RingCT/type: yes/0
Extra: 01ef519e04e1e25bf4d188374a5039631cb1032d0a973445bcdc5c90b53aff27ed021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fc8153cd01fe68d088e6d3dfc8c7d6caafdd3fb94f2a53d21f32b76d95f39c33 0.000600000000 1965051 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": 1475757, "vin": [ { "gen": { "height": 1475747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc8153cd01fe68d088e6d3dfc8c7d6caafdd3fb94f2a53d21f32b76d95f39c33" } } ], "extra": [ 1, 239, 81, 158, 4, 225, 226, 91, 244, 209, 136, 55, 74, 80, 57, 99, 28, 177, 3, 45, 10, 151, 52, 69, 188, 220, 92, 144, 181, 58, 255, 39, 237, 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) | dinastycoin version: tesla-369