← previous blocknext block →recent activity
Analyzing
Block #107,849,162
25 transactions · 18 stateful · 2026-09-25 08:47:39 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,849,162 · 25 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
3w06w08w19w211w212w313w415w016w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x327afab7…e5e5
0x34b655…2a6f
6 touches
3 conflicts
0xf75c3a6b…0568
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x54e6d2a8…ec22
0x34b655…2a6f
4 touches
1 conflict
0x70acaa64…c5ca
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
3 conflicts on slot 0x327afab79c…b1e5e5
Audit this contract →
← previous block·next block →recent activity