← previous blocknext block →recent activity
Analyzing
Block #107,817,231
23 transactions · 18 stateful · 2026-09-25 06:06:57 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,817,231 · 23 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
1w02w14w05w16w07w29w110w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0221d4b2…fcf9
0x34b655…2a6f
14 touches
21 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
14 touches
21 conflicts
0xa5811d93…8c73
0x34b655…2a6f
12 touches
15 conflicts
0x939cdd56…00c8
0x34b655…2a6f
12 touches
15 conflicts
0x925f5725…c40e
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x0df117a1…5fc4
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
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
21 conflicts on slot 0x0221d4b213…54fcf9
Audit this contract →
← previous block·next block →recent activity