← previous blocknext block →recent activity
Analyzing
Block #99,183,899
27 transactions · 20 stateful · 2026-08-26 00:18:34 UTC
Parallelism
89/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,183,899 · 27 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w012w013w114w015w118w119w020w121w022w223w125w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x3494b9e5…682b
0x851145…3f07
4 touches
1 conflict
0x48cf4743…bfe1
0x851145…3f07
4 touches
1 conflict
0xa6b936e6…22eb
0x851145…3f07
4 touches
1 conflict
0xb0370a35…157b
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity