Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 302c470bd2c6cea18f52b1e4eb0bd795f7e1f788f8c2d1ea76bc708cb4f299cc

Tx prefix hash: a987b81c771c47330542e19a0e7396a14e502282252e383bcf78bb21cde4ffb1
Tx public key: c49a713ef8e90df180bac4bf48d09a6794602979a0dc1a65ac3325c98532e18c
Timestamp: 1742063943 Timestamp [UTC]: 2025-03-15 18:39:03 Age [y:d:h:m:s]: 01:250:21:15:24
Block: 1240028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443466 RingCT/type: yes/0
Extra: 01c49a713ef8e90df180bac4bf48d09a6794602979a0dc1a65ac3325c98532e18c0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 43d7dc9b95370124c61b5cab0af9f99c3011bebbfe0d717d0d7d31293ab7bc12 0.000600000000 1726993 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": 1240038, "vin": [ { "gen": { "height": 1240028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d7dc9b95370124c61b5cab0af9f99c3011bebbfe0d717d0d7d31293ab7bc12" } } ], "extra": [ 1, 196, 154, 113, 62, 248, 233, 13, 241, 128, 186, 196, 191, 72, 208, 154, 103, 148, 96, 41, 121, 160, 220, 26, 101, 172, 51, 37, 201, 133, 50, 225, 140, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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: