← previous blocknext block →recent activity
Analyzing
Block #107,838,783
18 transactions · 16 stateful · 2026-09-25 07:55:25 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,838,783 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w110w211w313w414w515w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2c4d203…05b6
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xe1ce49dc…ae9d
0x34b655…2a6f
6 touches
3 conflicts
0x9b93123c…c650
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x2bd8c8ca…8dc6
0x34b655…2a6f
4 touches
1 conflict
0x221c5470…cda0
0x34b655…2a6f
4 touches
1 conflict
0x4d205b22…b005
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 0xa2c4d203df…b805b6
Audit this contract →
← previous block·next block →recent activity