Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e6bb34592fa2d68e98808444cae21ec248b30e89256f47d3b8923d71df3722

Tx prefix hash: 59801d746b5552c091afc679836a9cd1b1fed76b0213463c4962d2ed96d4d46b
Tx public key: 04e114ee815ce9d06613cd95c7557ead569ffb40338fcd8ee1eee492951c961b
Timestamp: 1703888554 Timestamp [UTC]: 2023-12-29 22:22:34 Age [y:d:h:m:s]: 02:324:21:48:49
Block: 923979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 757381 RingCT/type: yes/0
Extra: 0104e114ee815ce9d06613cd95c7557ead569ffb40338fcd8ee1eee492951c961b02110000000752d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c7b5f14c4bddb090fc5f67f7abf5ada6c7869ee745fb557aa4ae4e961c673ff6 0.000600000000 1381721 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": 923989, "vin": [ { "gen": { "height": 923979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7b5f14c4bddb090fc5f67f7abf5ada6c7869ee745fb557aa4ae4e961c673ff6" } } ], "extra": [ 1, 4, 225, 20, 238, 129, 92, 233, 208, 102, 19, 205, 149, 199, 85, 126, 173, 86, 159, 251, 64, 51, 143, 205, 142, 225, 238, 228, 146, 149, 28, 150, 27, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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: