← previous blocknext block →recent activity
Analyzing
Block #107,816,122
23 transactions · 19 stateful · 2026-09-25 06:01:22 UTC
Parallelism
91/100
Blocked
11%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,816,122 · 23 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
11w016w017w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x3a663e9a…a9cd
0x508254…98bd
4 touches
1 conflict
0x4d7f16b0…9f7f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x915c095e…c1e5
0x34ae4d…3fc5
2 touches
0 conflicts
0xcfe06a18…b5b5
0x34ae4d…3fc5
2 touches
0 conflicts
0xd8fd2add…50fc
0x34ae4d…3fc5
2 touches
0 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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity