Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99fbc11e1716b0a64fe3f008bfb771ad453a4577d73d75f5d0e504612e4a3ac5

Tx prefix hash: 1645ff708a06d23b6feacda39f6d1bdc49e9464f263aa2ec7222463d3bb34f51
Tx public key: 487451ac9af970cfe06c1c375669fe36c1425948d05f0d216cf2ade90de7abc6
Timestamp: 1744852282 Timestamp [UTC]: 2025-04-17 01:11:22 Age [y:d:h:m:s]: 01:024:07:45:25
Block: 1263088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268441 RingCT/type: yes/0
Extra: 01487451ac9af970cfe06c1c375669fe36c1425948d05f0d216cf2ade90de7abc6021100000003dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4a9a665229fe5f1a22119c13a0ef6dce188244cb0e75b846e92c7db08d0b8969 0.000600000000 1750271 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": 1263098, "vin": [ { "gen": { "height": 1263088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9a665229fe5f1a22119c13a0ef6dce188244cb0e75b846e92c7db08d0b8969" } } ], "extra": [ 1, 72, 116, 81, 172, 154, 249, 112, 207, 224, 108, 28, 55, 86, 105, 254, 54, 193, 66, 89, 72, 208, 95, 13, 33, 108, 242, 173, 233, 13, 231, 171, 198, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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: