← previous blocknext block →recent activity
Analyzing
Block #105,575,341
16 transactions · 16 stateful · 2026-09-17 09:57:12 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,575,341 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4e632c…e14c
0x34b655…2a6f
8 touches
6 conflicts
0xdac7e046…6ea7
0x34b655…2a6f
6 touches
3 conflicts
0xd3d054d7…4bfb
0x37db7f…ec7b
6 touches
3 conflicts
0xdad13823…6798
0x37db7f…ec7b
6 touches
3 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
6 touches
3 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
6 touches
3 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
6 touches
3 conflicts
0x75f36d60…8556
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 0xfd4e632c76…e1e14c
Audit this contract →
← previous block·next block →recent activity