← previous blocknext block →recent activity
Analyzing
Block #106,308,242
21 transactions · 20 stateful · 2026-09-19 23:28:24 UTC
Parallelism
76/100
Blocked
30%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,308,242 · 21 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
1w02w16w210w313w318w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x630dc607…7cc8
0x34b655…2a6f
10 touches
10 conflicts
0xc389d1ff…6a00
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x81878590…6d25
0x34b655…2a6f
6 touches
3 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x07c47b1c…93c8
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 0x630dc60706…b27cc8
Audit this contract →
← previous block·next block →recent activity