Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 761dd57d40116d7030152f5e5e20239ad5f4abe73e1eb6230c9fabd2b13791f8

Tx prefix hash: 98c50a6e9dca1e4ecf465f62130cb748083c28e7d5196d458cd8971f64c3b962
Tx public key: fc90eeb6c6d283e824d4a2ec4df7e8300b4791271b0aada70cd0791feafd271f
Timestamp: 1775103973 Timestamp [UTC]: 2026-04-02 04:26:13 Age [y:d:h:m:s]: 00:144:15:37:02
Block: 1510977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109200 RingCT/type: yes/0
Extra: 01fc90eeb6c6d283e824d4a2ec4df7e8300b4791271b0aada70cd0791feafd271f021100000002ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6719de992c3b92662efad4f96d93ffc09cece3b43b2fac56e2acad4c2a9c4074 0.000600000000 2000763 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": 1510987, "vin": [ { "gen": { "height": 1510977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6719de992c3b92662efad4f96d93ffc09cece3b43b2fac56e2acad4c2a9c4074" } } ], "extra": [ 1, 252, 144, 238, 182, 198, 210, 131, 232, 36, 212, 162, 236, 77, 247, 232, 48, 11, 71, 145, 39, 27, 10, 173, 167, 12, 208, 121, 31, 234, 253, 39, 31, 2, 17, 0, 0, 0, 2, 238, 75, 113, 129, 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: