← previous blocknext block →recent activity
Analyzing
Block #106,282,260
26 transactions · 24 stateful · 2026-09-19 21:17:39 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,282,260 · 26 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
1w03w04w05w18w09w110w211w312w313w414w515w616w623w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1f74b16…ee81
0x34b655…2a6f
14 touches
21 conflicts
0x38c6ff01…689f
0x34b655…2a6f
10 touches
10 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x26867cdc…dab5
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xc1f74b16dc…d2ee81
Audit this contract →
← previous block·next block →recent activity