← previous blocknext block →recent activity
Analyzing
Block #93,557,911
18 transactions · 17 stateful · 2026-08-06 06:08:42 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,557,911 · 18 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
4w05w16w27w09w010w112w113w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x78860c4f…cade
0x34b655…2a6f
4 touches
1 conflict
0x7f022029…89f0
0x34b655…2a6f
4 touches
1 conflict
0x80bf58f2…be95
0x34b655…2a6f
4 touches
1 conflict
0x80bf58f2…be96
0x34b655…2a6f
4 touches
1 conflict
0x9769421a…9da5
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
3 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity