Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2540ba7e05d9e15d675b53dbe7b0a44e9feb40c5e712b33aab33b662f63e3f31

Tx prefix hash: 99e5a5f0ab37ce6049b3bd0f772dbefe47d65a39501122589682935519f720cf
Tx public key: eb468de6f01c397fb44cf3464f799b09cedd81b1e7101b80ea6a39b0cf00bd61
Timestamp: 1750026829 Timestamp [UTC]: 2025-06-15 22:33:49 Age [y:d:h:m:s]: 00:336:13:25:48
Block: 1305833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230807 RingCT/type: yes/0
Extra: 01eb468de6f01c397fb44cf3464f799b09cedd81b1e7101b80ea6a39b0cf00bd6102110000000e43846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 47d0dfd080577c6f94bcfb936773de77427d3028979b45baaccc3ee1a18dcb2e 0.000600000000 1793434 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": 1305843, "vin": [ { "gen": { "height": 1305833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47d0dfd080577c6f94bcfb936773de77427d3028979b45baaccc3ee1a18dcb2e" } } ], "extra": [ 1, 235, 70, 141, 230, 240, 28, 57, 127, 180, 76, 243, 70, 79, 121, 155, 9, 206, 221, 129, 177, 231, 16, 27, 128, 234, 106, 57, 176, 207, 0, 189, 97, 2, 17, 0, 0, 0, 14, 67, 132, 109, 102, 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: