← previous blocknext block →recent activity
Analyzing
Block #106,916,071
21 transactions · 21 stateful · 2026-09-22 02:28:38 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,916,071 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w17w08w19w210w311w312w413w514w615w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c60fbcf…8744
0x34b655…2a6f
10 touches
10 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xe6a595bf…3c45
0x34b655…2a6f
8 touches
6 conflicts
0x158cd73a…d47b
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xfb92aed5…aa1f
0x34b655…2a6f
4 touches
1 conflict
0x4870c9a7…ef7c
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 0x6c60fbcffc…878744
Audit this contract →
← previous block·next block →recent activity