Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef1143b5edeb1af8901deca35dc7e2ce703057884520d766e93ef096b28a607

Tx prefix hash: 25aa53fe079425f61229bc4ea66ed4b27aed5ef0ad2fa014ba67730a713a2c95
Tx public key: c263826153e4db89b1b3d6779fe96d159ada4f3d16653bdfae6f7fb813670ccf
Timestamp: 1709040298 Timestamp [UTC]: 2024-02-27 13:24:58 Age [y:d:h:m:s]: 02:268:03:06:55
Block: 966701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 716793 RingCT/type: yes/0
Extra: 01c263826153e4db89b1b3d6779fe96d159ada4f3d16653bdfae6f7fb813670ccf02110000000f0011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 24fb0870598a247482489c02dc237870f38389c1cd43e77f0940318bc7c33bb6 0.000600000000 1426472 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": 966711, "vin": [ { "gen": { "height": 966701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24fb0870598a247482489c02dc237870f38389c1cd43e77f0940318bc7c33bb6" } } ], "extra": [ 1, 194, 99, 130, 97, 83, 228, 219, 137, 177, 179, 214, 119, 159, 233, 109, 21, 154, 218, 79, 61, 22, 101, 59, 223, 174, 111, 127, 184, 19, 103, 12, 207, 2, 17, 0, 0, 0, 15, 0, 17, 5, 91, 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: