← previous blocknext block →recent activity
Analyzing
Block #106,916,513
25 transactions · 24 stateful · 2026-09-22 02:30:51 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.48
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,916,513 · 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
1w02w16w07w18w29w310w211w412w513w614w715w818w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ca1284…cb2c
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xf782ee27…41cd
0x34b655…2a6f
12 touches
15 conflicts
0x51087f5a…61f7
0x34b655…2a6f
10 touches
10 conflicts
0x803d32b5…8094
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x0c17a749…8012
0x34b655…2a6f
6 touches
3 conflicts
0xa37ee838…b19b
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
21 conflicts on slot 0x53ca128412…cacb2c
Audit this contract →
← previous block·next block →recent activity