← previous blocknext block →recent activity
Analyzing
Block #93,364,045
11 transactions · 10 stateful · 2026-08-05 13:54:04 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,364,045 · 11 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
1w02w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfecb18c0…01ed
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x5a746750…e0fb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5b9528ae…c472
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
2 touches
0 conflicts
0xa42e6eab…c84d
0x34b655…2a6f
2 touches
0 conflicts
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
6 conflicts on slot 0xfecb18c068…6e01ed
Audit this contract →
← previous block·next block →recent activity