← previous blocknext block →recent activity
Analyzing
Block #106,234,996
35 transactions · 33 stateful · 2026-09-19 17:19:49 UTC
Parallelism
71/100
Blocked
70%
Avg conflicts / tx
2.26
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,234,996 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w09w110w311w412w518w119w420w521w622w723w824w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1010e810…784f
0x34b655…2a6f
18 touches
36 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
8 touches
6 conflicts
0x05e1eba1…6491
0x34b655…2a6f
8 touches
6 conflicts
0xe2ce5557…ab10
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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
36 conflicts on slot 0x1010e81088…d8784f
Audit this contract →
← previous block·next block →recent activity