← previous blocknext block →recent activity
Analyzing
Block #105,855,589
28 transactions · 25 stateful · 2026-09-18 09:29:12 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,855,589 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w010w011w115w117w218w319w420w524w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf34bbcd…b681
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x14fdfaf5…4469
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0x9c83a7b1…e305
0x34b655…2a6f
8 touches
6 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
6 touches
3 conflicts
0x89999c15…fdac
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
10 conflicts on slot 0xcf34bbcd6f…d2b681
Audit this contract →
← previous block·next block →recent activity