← previous blocknext block →recent activity
Analyzing
Block #106,215,672
26 transactions · 24 stateful · 2026-09-19 15:42:30 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,215,672 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w38w09w119w421w022w125w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x08f9abf1…10bf
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x4de0b2a2…784f
0xc8689a…ee79
4 touches
1 conflict
0x08c3e5cd…32d4
0x34b655…2a6f
4 touches
1 conflict
0x1f91b1ad…349a
0x34b655…2a6f
4 touches
1 conflict
0x47c4f650…509c
0x37db7f…ec7b
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity