← previous blocknext block →recent activity
Analyzing
Block #107,839,012
25 transactions · 23 stateful · 2026-09-25 07:56:34 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,839,012 · 25 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
2w03w05w19w012w213w114w115w016w017w218w119w322w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2c4d203…05b6
0x34b655…2a6f
8 touches
6 conflicts
0x25144f94…1854
0x34b655…2a6f
6 touches
3 conflicts
0x81ca07cc…c115
0x34b655…2a6f
6 touches
3 conflicts
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x34c7c0ef…0178
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x7ed4080f…0f62
0x34b655…2a6f
4 touches
1 conflict
0x901ee5a6…347a
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 0xa2c4d203df…b805b6
Audit this contract →
← previous block·next block →recent activity