Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c6cfb9c0312ab898e2161b7bc27eecfad75862001ae912f47ebf6a335319d5e

Tx prefix hash: 7529d41163df6b892205d09401d3e10eb0db22eff080f85bb2c3306ddb707d6a
Tx public key: 01efcbfb90d7aa17fb0f702c8410c614c47ffa2bcf1c4d170a8c33e11a021236
Timestamp: 1710408428 Timestamp [UTC]: 2024-03-14 09:27:08 Age [y:d:h:m:s]: 02:253:06:59:14
Block: 978056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705438 RingCT/type: yes/0
Extra: 0101efcbfb90d7aa17fb0f702c8410c614c47ffa2bcf1c4d170a8c33e11a02123602110000000359dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1b5cd25f12e79aad9fafd49f698026d7cbf1e55ce10324f94f629cfc1c416230 0.000600000000 1438073 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": 978066, "vin": [ { "gen": { "height": 978056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b5cd25f12e79aad9fafd49f698026d7cbf1e55ce10324f94f629cfc1c416230" } } ], "extra": [ 1, 1, 239, 203, 251, 144, 215, 170, 23, 251, 15, 112, 44, 132, 16, 198, 20, 196, 127, 250, 43, 207, 28, 77, 23, 10, 140, 51, 225, 26, 2, 18, 54, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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: