← previous blocknext block →recent activity
Analyzing
Block #107,838,402
28 transactions · 21 stateful · 2026-09-25 07:53:30 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,838,402 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w210w011w112w213w314w415w516w617w725w026w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x25144f94…1854
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3d5599a7…2386
0x34b655…2a6f
4 touches
1 conflict
0x4d205b22…b005
0x34b655…2a6f
4 touches
1 conflict
0x64141a92…64fd
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
6 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity