← previous blocknext block →recent activity
Analyzing
Block #106,282,495
20 transactions · 19 stateful · 2026-09-19 21:18:50 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,282,495 · 20 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
1w02w13w14w27w08w19w214w215w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
8 touches
6 conflicts
0xf820a074…e5b6
0x34b655…2a6f
8 touches
6 conflicts
0x224c539c…d9f2
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
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
6 conflicts on slot 0x85eb131679…60bb9e
Audit this contract →
← previous block·next block →recent activity