← previous blocknext block →recent activity
Analyzing
Block #105,881,042
17 transactions · 14 stateful · 2026-09-18 11:37:17 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,881,042 · 17 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
1w05w16w211w312w413w514w615w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91c52f63…8216
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
6 touches
3 conflicts
0xf8e6479f…f193
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x3352001f…4665
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc389d1ff…6a00
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
6 conflicts on slot 0x91c52f6362…358216
Audit this contract →
← previous block·next block →recent activity