← previous blocknext block →recent activity
Analyzing
Block #107,815,346
21 transactions · 18 stateful · 2026-09-25 05:57:27 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,815,346 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w18w09w111w212w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x2d0d6e63…0ffc
0x34b655…2a6f
6 touches
3 conflicts
0xa23b9051…392f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
6 touches
3 conflicts
0x28e2f7c3…e848
0x34b655…2a6f
4 touches
1 conflict
0x2a880840…7365
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
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