← previous blocknext block →recent activity
Analyzing
Block #106,393,267
24 transactions · 21 stateful · 2026-09-20 06:36:18 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,393,267 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w29w010w114w015w116w219w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d175439…fb79
0x34b655…2a6f
8 touches
6 conflicts
0x54563e2b…7469
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0xde00fca6…3969
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
6 touches
3 conflicts
0xdd77da90…6df4
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
6 conflicts on slot 0x8d17543904…b6fb79
Audit this contract →
← previous block·next block →recent activity