← previous blocknext block →recent activity
Analyzing
Block #107,816,050
23 transactions · 18 stateful · 2026-09-25 06:01:00 UTC
Parallelism
87/100
Blocked
22%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,816,050 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w08w19w010w211w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bd71786…2d83
0x34b655…2a6f
6 touches
3 conflicts
0xf7a913e7…2568
0x34b655…2a6f
6 touches
3 conflicts
0x3a663e9a…a9d1
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9cd
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9ce
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9d0
0x508254…98bd
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
3 conflicts on slot 0x2bd7178683…a02d83
Audit this contract →
← previous block·next block →recent activity