← previous blocknext block →recent activity
Analyzing
Block #106,542,392
23 transactions · 23 stateful · 2026-09-20 19:06:52 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,542,392 · 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
1w02w03w04w16w17w210w211w312w113w414w415w516w620w322w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa829beb3…ef5e
0x34b655…2a6f
12 touches
15 conflicts
0x76ed17bf…9bd8
0x34b655…2a6f
10 touches
10 conflicts
0x735a86cd…b64d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
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 0xa829beb30d…48ef5e
Audit this contract →
← previous block·next block →recent activity