← previous blocknext block →recent activity
Analyzing
Block #107,823,411
30 transactions · 19 stateful · 2026-09-25 06:38:03 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #107,823,411 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w510w611w713w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ed4080f…0f62
0x34b655…2a6f
14 touches
21 conflicts
0x40226f40…3182
0x34b655…2a6f
8 touches
6 conflicts
0xa5811d93…8c73
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
8 touches
6 conflicts
0x20492d53…80f9
0x34b655…2a6f
6 touches
3 conflicts
0x33848157…61dc
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 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 0x7ed4080f1a…750f62
Audit this contract →
← previous block·next block →recent activity