← previous blocknext block →recent activity
Analyzing
Block #106,273,086
37 transactions · 35 stateful · 2026-09-19 20:31:30 UTC
Parallelism
68/100
Blocked
71%
Avg conflicts / tx
2.11
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,273,086 · 37 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w27w310w111w213w014w116w217w318w319w420w521w624w825w926w1027w1133w536w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66b9c723…a1a0
0x34b655…2a6f
12 touches
15 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
10 touches
10 conflicts
0x0fc536fb…1aa1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xdb0f2d37…bebb
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xba65d335…5a78
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 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
15 conflicts on slot 0x66b9c7234a…cca1a0
Audit this contract →
← previous block·next block →recent activity