← previous blocknext block →recent activity
Analyzing
Block #99,038,750
21 transactions · 20 stateful · 2026-08-25 12:04:41 UTC
Parallelism
76/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,038,750 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w09w110w011w213w115w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3843ecd7…b420
0x8964d7…10f8
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x3843ecd7…b41b
0x8964d7…10f8
4 touches
1 conflict
0x3843ecd7…b41c
0x8964d7…10f8
4 touches
1 conflict
0x3843ecd7…b41f
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x3843ecd7f6…58b420
Audit this contract →
← previous block·next block →recent activity