Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccfecd3263d813f1667b1d5e9cab2526535c2d15888e91ea229ddf52b3f68507

Tx prefix hash: b0203481fff66a49ddbbdc56f9f0b99e1eee6e1d138d3e7b97456761b60d64b3
Tx public key: ef44de004b58b03721c542f8a2a79e412cd74095bb3c33b478c7d9530c22ead8
Timestamp: 1740673382 Timestamp [UTC]: 2025-02-27 16:23:02 Age [y:d:h:m:s]: 01:151:00:18:08
Block: 1228483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371957 RingCT/type: yes/0
Extra: 01ef44de004b58b03721c542f8a2a79e412cd74095bb3c33b478c7d9530c22ead80211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 11c3482636287db28c37e1dcc243918423e63819ec5d66b62265945e5d5a7f79 0.000600000000 1715364 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": 1228493, "vin": [ { "gen": { "height": 1228483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11c3482636287db28c37e1dcc243918423e63819ec5d66b62265945e5d5a7f79" } } ], "extra": [ 1, 239, 68, 222, 0, 75, 88, 176, 55, 33, 197, 66, 248, 162, 167, 158, 65, 44, 215, 64, 149, 187, 60, 51, 180, 120, 199, 217, 83, 12, 34, 234, 216, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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: