← previous blocknext block →recent activity
Analyzing
Block #107,640,417
19 transactions · 19 stateful · 2026-09-24 15:15:34 UTC
Parallelism
79/100
Blocked
16%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,640,417 · 19 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
5w06w115w016w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0ee5647…6324
0x34b655…2a6f
6 touches
3 conflicts
0x6780726b…4864
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe226a0be…c046
0x34b655…2a6f
6 touches
3 conflicts
0x100812e9…12b7
0x34b655…2a6f
6 touches
3 conflicts
0x74cdc294…26a8
0x34b655…2a6f
4 touches
1 conflict
0x98dd86bb…1edb
0x34b655…2a6f
4 touches
1 conflict
0x9d6a99f9…da64
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 0xf0ee564725…b96324
Audit this contract →
← previous block·next block →recent activity