← previous blocknext block →recent activity
Analyzing
Block #106,252,574
23 transactions · 22 stateful · 2026-09-19 18:48:17 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,252,574 · 23 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
1w02w13w04w16w08w19w210w012w113w215w316w417w518w622w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa887d34a…2e8a
0x34b655…2a6f
14 touches
21 conflicts
0x5717771c…45ed
0x34b655…2a6f
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x59ec0dd4…543c
0x34b655…2a6f
6 touches
3 conflicts
0x6b267bdf…b173
0x34b655…2a6f
6 touches
3 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
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
21 conflicts on slot 0xa887d34a3a…a32e8a
Audit this contract →
← previous block·next block →recent activity