← previous blocknext block →recent activity
Analyzing
Block #93,474,873
13 transactions · 13 stateful · 2026-08-05 23:11:16 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,474,873 · 13 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
1w02w13w04w07w18w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427dec7f…61c6
0x34b655…2a6f
6 touches
3 conflicts
0x6d8bf82a…3f56
0x99c7a7…8bf0
4 touches
1 conflict
0x91e8d927…3a11
0x34b655…2a6f
4 touches
1 conflict
0x9c26cddd…9972
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x7aa512ae…d2e0
0x754704…b603
4 touches
1 conflict
0x7f03e539…f4cc
0x754704…b603
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
3 conflicts on slot 0x427dec7fbc…3e61c6
Audit this contract →
← previous block·next block →recent activity