← previous blocknext block →recent activity
Analyzing
Block #107,441,802
13 transactions · 13 stateful · 2026-09-23 22:35:15 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,441,802 · 13 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
1w05w16w27w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x125c7c50…0287
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0x1ad8153e…06bf
0x34b655…2a6f
4 touches
1 conflict
0x3b8da5cc…e045
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x68da92a9…a853
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 0x125c7c506c…780287
Audit this contract →
← previous block·next block →recent activity