← previous blocknext block →recent activity
Analyzing
Block #105,436,016
25 transactions · 20 stateful · 2026-09-16 22:16:03 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.92
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,436,016 · 25 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
3w05w17w216w217w318w421w522w623w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89bc46ca…94c4
0x34b655…2a6f
10 touches
10 conflicts
0x0f5d9d18…94a8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0xd1448207…452d
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xca841faa…486a
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
10 conflicts on slot 0x89bc46ca21…b394c4
Audit this contract →
← previous block·next block →recent activity