Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f54237e9476f82db8cdbd70718e048fe7e56e20cff5756d48d1cd394decee315

Tx prefix hash: 32a09962d0cfd0746a6da7b114a9081e7d7b91c6b00736bee0554a8266a03c50
Tx public key: a5c6b13d526f6f1d10458337680f1faafff187f15782e1180d74d643e8414d1a
Timestamp: 1747222631 Timestamp [UTC]: 2025-05-14 11:37:11 Age [y:d:h:m:s]: 01:184:09:20:50
Block: 1282713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395686 RingCT/type: yes/0
Extra: 01a5c6b13d526f6f1d10458337680f1faafff187f15782e1180d74d643e8414d1a0211000000061f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2c53cfc521dbf3367c793ea0a7c49f6fd5defa5b44fb58ff6b23702ddecca3c1 0.000600000000 1770122 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": 1282723, "vin": [ { "gen": { "height": 1282713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c53cfc521dbf3367c793ea0a7c49f6fd5defa5b44fb58ff6b23702ddecca3c1" } } ], "extra": [ 1, 165, 198, 177, 61, 82, 111, 111, 29, 16, 69, 131, 55, 104, 15, 31, 170, 255, 241, 135, 241, 87, 130, 225, 24, 13, 116, 214, 67, 232, 65, 77, 26, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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: