← previous blocknext block →recent activity
Analyzing
Block #93,928,209
11 transactions · 9 stateful · 2026-08-07 13:10:44 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,928,209 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7908b5f…56b9
0x34b655…2a6f
4 touches
1 conflict
0x1438d03e…4250
0x34b655…2a6f
4 touches
1 conflict
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x3df47518…17f8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
1 conflict on slot 0xd7908b5fe5…2b56b9
Audit this contract →
← previous block·next block →recent activity