← previous blocknext block →recent activity
Analyzing
Block #107,816,024
25 transactions · 21 stateful · 2026-09-25 06:00:52 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,816,024 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w29w010w111w212w213w316w322w023w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x2a0b926a…1b4b
0x34b655…2a6f
4 touches
1 conflict
0x379e77ed…b222
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
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 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity