← previous blocknext block →recent activity
Analyzing
Block #106,921,783
25 transactions · 24 stateful · 2026-09-22 02:57:22 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,921,783 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w18w29w310w411w512w613w714w821w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c60fbcf…8744
0x34b655…2a6f
12 touches
15 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
10 touches
10 conflicts
0x4f89250b…4bb2
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x8f4be1ed…2e29
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf5547123…bec8
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
15 conflicts on slot 0x6c60fbcffc…878744
Audit this contract →
← previous block·next block →recent activity