← previous blocknext block →recent activity
Analyzing
Block #93,847,046
14 transactions · 13 stateful · 2026-08-07 06:22:15 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,847,046 · 14 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
1w03w04w15w29w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd5e7e0c…b81d
0x34b655…2a6f
6 touches
3 conflicts
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
4 touches
1 conflict
0x5d46e6a0…5ed9
0x40c49f…2af0
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf15273a1…2c52
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xfd5e7e0c4d…7ab81d
Audit this contract →
← previous block·next block →recent activity