← previous blocknext block →recent activity
Analyzing
Block #107,848,093
27 transactions · 21 stateful · 2026-09-25 08:42:17 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,848,093 · 27 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
6w08w19w212w013w114w215w116w217w324w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1abfd3ae…2999
0x34b655…2a6f
4 touches
1 conflict
0x28cc3b1e…9229
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x36dc68d2…2f3e
0x34b655…2a6f
4 touches
1 conflict
0x4155e64d…1d89
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity