← previous blocknext block →recent activity
Analyzing
Block #93,236,811
11 transactions · 9 stateful · 2026-08-05 03:14:21 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,236,811 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfecb18c0…01ed
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0d0070b9…33b7
0x34b655…2a6f
4 touches
1 conflict
0x0e2c8224…e84b
0x34b655…2a6f
4 touches
1 conflict
0x231ccc13…a7c6
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0x84ee6168…3f13
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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
1 conflict on slot 0xfecb18c068…6e01ed
Audit this contract →
← previous block·next block →recent activity