← previous blocknext block →recent activity
Analyzing
Block #107,813,616
16 transactions · 16 stateful · 2026-09-25 05:48:45 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,813,616 · 16 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
4w05w110w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
10 touches
10 conflicts
0xd87f1ed1…59f0
0x34b655…2a6f
10 touches
10 conflicts
0x961c0cd9…0937
0x34b655…2a6f
10 touches
10 conflicts
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x5aa6edce…0840
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xe63c6702…03f3
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
10 conflicts on slot 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity