← previous blocknext block →recent activity
Analyzing
Block #106,922,084
21 transactions · 21 stateful · 2026-09-22 02:58:53 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,922,084 · 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
1w02w16w08w110w011w112w213w314w415w516w619w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0x93e4c736…3731
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x6cf9c605…7b8f
0x34b655…2a6f
6 touches
3 conflicts
0x47f2c990…af1e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity