Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6245465cf6487e9974d4043ba43dcb3a6ee7a49e28e1c541d4f32376fb95643

Tx prefix hash: 5204c13d52857e36243ee2edf5b5510d3f7f4aa28cffa1e96a1a565ad08ceb8e
Tx public key: 4476a26241a0d0cdf9c010134ab6bc5397a8afb8654e68940d369dfb62fc69e8
Timestamp: 1746934290 Timestamp [UTC]: 2025-05-11 03:31:30 Age [y:d:h:m:s]: 01:008:08:41:36
Block: 1280326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257923 RingCT/type: yes/0
Extra: 014476a26241a0d0cdf9c010134ab6bc5397a8afb8654e68940d369dfb62fc69e80211000000071f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 680157d26b48b214effe73fdbc23159b2e2e8223fd440ea5b1de5c46bdeabf57 0.000600000000 1767709 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": 1280336, "vin": [ { "gen": { "height": 1280326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "680157d26b48b214effe73fdbc23159b2e2e8223fd440ea5b1de5c46bdeabf57" } } ], "extra": [ 1, 68, 118, 162, 98, 65, 160, 208, 205, 249, 192, 16, 19, 74, 182, 188, 83, 151, 168, 175, 184, 101, 78, 104, 148, 13, 54, 157, 251, 98, 252, 105, 232, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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: