← previous blocknext block →recent activity
Analyzing
Block #106,028,456
20 transactions · 19 stateful · 2026-09-19 00:00:16 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,028,456 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w07w18w29w313w114w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
6 touches
3 conflicts
0x238d0a65…428b
0x37db7f…ec7b
6 touches
3 conflicts
0xd3d054d7…4bfb
0x37db7f…ec7b
6 touches
3 conflicts
0xdad13823…6798
0x37db7f…ec7b
6 touches
3 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x12e77486…ec2b
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity