← previous blocknext block →recent activity
Analyzing
Block #106,419,955
19 transactions · 19 stateful · 2026-09-20 08:50:36 UTC
Parallelism
53/100
Blocked
58%
Avg conflicts / tx
2.11
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,419,955 · 19 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
2w04w16w27w38w49w413w214w515w617w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbd130fe…a03c
0x34b655…2a6f
16 touches
28 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
10 touches
10 conflicts
0x6d955786…1327
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xf171f918…801d
0x34b655…2a6f
6 touches
3 conflicts
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
28 conflicts on slot 0xdbd130fe8e…24a03c
Audit this contract →
← previous block·next block →recent activity