← previous blocknext block →recent activity
Analyzing
Block #106,419,755
17 transactions · 17 stateful · 2026-09-20 08:49:36 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,419,755 · 17 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
1w02w04w16w27w38w49w511w112w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb8af573…a855
0x34b655…2a6f
14 touches
21 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
8 touches
6 conflicts
0x2029b74e…c206
0x34b655…2a6f
6 touches
3 conflicts
0xb9b077a8…e029
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b25f260…c429
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 0xeb8af57324…0fa855
Audit this contract →
← previous block·next block →recent activity