← previous blocknext block →recent activity
Analyzing
Block #106,935,481
21 transactions · 20 stateful · 2026-09-22 04:06:19 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,935,481 · 21 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
1w02w13w04w16w09w110w215w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57bf1a1b…914e
0x34b655…2a6f
10 touches
10 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x7fc8f46e…0f75
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
10 conflicts on slot 0x57bf1a1bda…90914e
Audit this contract →
← previous block·next block →recent activity