Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 394aceb21d4c5b769d9eed0dcdd7df99cbaec96281c6ae3a48b7bf6a2ea97690

Tx prefix hash: 28ce387cad4452b530ab6df17a2829b4b6a2c2e951e96d8059c0693d43da09ad
Tx public key: 66dc153ef811c8eba8cb49f439bd21379efba57f2c7e5c81f4a967d622d15f1b
Timestamp: 1738291867 Timestamp [UTC]: 2025-01-31 02:51:07 Age [y:d:h:m:s]: 01:292:09:11:15
Block: 1208781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473093 RingCT/type: yes/0
Extra: 0166dc153ef811c8eba8cb49f439bd21379efba57f2c7e5c81f4a967d622d15f1b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2bf3966e6345bf5e816c106aea1afc0afad0237d01498ee9ed08a80ffcfba29b 0.000600000000 1695516 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": 1208791, "vin": [ { "gen": { "height": 1208781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bf3966e6345bf5e816c106aea1afc0afad0237d01498ee9ed08a80ffcfba29b" } } ], "extra": [ 1, 102, 220, 21, 62, 248, 17, 200, 235, 168, 203, 73, 244, 57, 189, 33, 55, 158, 251, 165, 127, 44, 126, 92, 129, 244, 169, 103, 214, 34, 209, 95, 27, 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: