← previous blocknext block →recent activity
Analyzing
Block #94,852,773
10 transactions · 10 stateful · 2026-08-10 18:58:30 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,852,773 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a377d1e…36e4
0x34b655…2a6f
4 touches
1 conflict
0xf7cea934…5fe9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd957c18f…5cfc
0x34b655…2a6f
4 touches
1 conflict
0x0df128be…951d
0x34b655…2a6f
2 touches
0 conflicts
0x1490544d…0827
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x418f6232…2de6
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 0x1a377d1e0a…6f36e4
Audit this contract →
← previous block·next block →recent activity