← previous blocknext block →recent activity
Analyzing
Block #93,321,067
9 transactions · 8 stateful · 2026-08-05 10:17:59 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,321,067 · 9 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69473e5b…cb2a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x6bf457e3…9576
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
2 touches
0 conflicts
0x6d74089c…c836
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x8289c329…644f
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 0x69473e5b4a…8ccb2a
Audit this contract →
← previous block·next block →recent activity