← previous blocknext block →recent activity
Analyzing
Block #105,880,421
23 transactions · 20 stateful · 2026-09-18 11:34:10 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,880,421 · 23 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
2w03w04w05w16w07w112w014w215w316w417w518w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97e4c862…4419
0x34b655…2a6f
14 touches
21 conflicts
0x724b4cf4…70ef
0x34b655…2a6f
8 touches
6 conflicts
0x54b470ca…ff73
0x34b655…2a6f
8 touches
6 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0xcdbeed8b…6369
0x34b655…2a6f
6 touches
3 conflicts
0x931975c2…b7b3
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x97e4c86258…af4419
Audit this contract →
← previous block·next block →recent activity