← previous blocknext block →recent activity
Analyzing
Block #99,038,228
22 transactions · 18 stateful · 2026-08-25 12:02:02 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,038,228 · 22 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
1w04w19w010w011w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f5ae5ec…2c7d
0x34b655…2a6f
4 touches
1 conflict
0x46e2bb67…d8b3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x91508d45…318b
0x34b655…2a6f
4 touches
1 conflict
0xab60dc09…85e4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe3684e08…c96a
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: Perpl
1 conflict on slot 0x3f5ae5ec31…072c7d
Audit this contract →
← previous block·next block →recent activity