← previous blocknext block →recent activity
Analyzing
Block #93,854,304
10 transactions · 9 stateful · 2026-08-07 06:58:44 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,854,304 · 10 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
1w02w14w06w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0xb1b58b33…874f
0x34b655…2a6f
4 touches
1 conflict
0xd5fedb27…4eea
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0xa3c36de0…3cf3
0x34b655…2a6f
2 touches
0 conflicts
0xa5ab7b8a…c97b
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
1 conflict on slot 0x2328941c9c…fc84d3
Audit this contract →
← previous block·next block →recent activity