← previous blocknext block →recent activity
Analyzing
Block #99,952,888
24 transactions · 22 stateful · 2026-08-28 17:03:04 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,952,888 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w28w29w312w413w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xead15497…1dbe
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x372c0c2c…abf9
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xa1731f0f…1f9d
0x34b655…2a6f
4 touches
1 conflict
0xb240b520…a88a
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
15 conflicts on slot 0xead15497a3…971dbe
Audit this contract →
← previous block·next block →recent activity