Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2963e30fddfdedbb154bf60160695c1e45d31beedf592b075223ee96b960318f

Tx prefix hash: fca7d880c3bc1a4cb43f251db8b1d8eac846b959b3f7cae2e37162acf7437160
Tx public key: 4da3fedbbd9b80a3edbbec1282bc053e73ee81ea7c09aedcb7904103326050c3
Timestamp: 1747137155 Timestamp [UTC]: 2025-05-13 11:52:35 Age [y:d:h:m:s]: 01:076:05:07:15
Block: 1282006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318434 RingCT/type: yes/0
Extra: 014da3fedbbd9b80a3edbbec1282bc053e73ee81ea7c09aedcb7904103326050c30211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cc02491c4c36ec9289617578930f5b6494498b4a214f39b5744f780911fa0d08 0.000600000000 1769413 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": 1282016, "vin": [ { "gen": { "height": 1282006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc02491c4c36ec9289617578930f5b6494498b4a214f39b5744f780911fa0d08" } } ], "extra": [ 1, 77, 163, 254, 219, 189, 155, 128, 163, 237, 187, 236, 18, 130, 188, 5, 62, 115, 238, 129, 234, 124, 9, 174, 220, 183, 144, 65, 3, 50, 96, 80, 195, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: