← previous blocknext block →recent activity
Analyzing
Block #106,393,351
17 transactions · 16 stateful · 2026-09-20 06:36:43 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,393,351 · 17 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
2w04w05w16w011w112w113w214w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9a6e112…69cc
0x34b655…2a6f
8 touches
6 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x811cb01f…e507
0x34b655…2a6f
4 touches
1 conflict
0x8d175439…fb79
0x34b655…2a6f
4 touches
1 conflict
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
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 0xc9a6e112ce…9769cc
Audit this contract →
← previous block·next block →recent activity