← previous blocknext block →recent activity
Analyzing
Block #106,452,783
19 transactions · 18 stateful · 2026-09-20 11:35:53 UTC
Parallelism
58/100
Blocked
56%
Avg conflicts / tx
1.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,452,783 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w18w09w110w211w313w414w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x852ca66a…f357
0x34b655…2a6f
16 touches
28 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
10 touches
10 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
6 touches
3 conflicts
0x07610b8e…6093
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
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 0x852ca66a2d…bcf357
Audit this contract →
← previous block·next block →recent activity