← previous blocknext block →recent activity
Analyzing
Block #107,823,242
33 transactions · 24 stateful · 2026-09-25 06:37:12 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,823,242 · 33 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
1w05w07w08w118w019w120w121w222w323w426w027w131w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xdcd07321…1c31
0x34b655…2a6f
6 touches
3 conflicts
0xfa16f3ac…c002
0xd32edf…ff58
5 touches
3 conflicts
0x3aed9088…e43c
0x34b655…2a6f
4 touches
1 conflict
0x41eb76a7…6483
0x34b655…2a6f
4 touches
1 conflict
0x422cccbc…9b18
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 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity