← previous blocknext block →recent activity
Analyzing
Block #93,369,113
14 transactions · 12 stateful · 2026-08-05 14:19:33 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,369,113 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde9cde5…4cff
0x34b655…2a6f
8 touches
6 conflicts
0xa279b18d…63bc
0x34b655…2a6f
6 touches
3 conflicts
0x283a662b…c457
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x37e68458…04ad
0x34b655…2a6f
4 touches
1 conflict
0x40fcd437…9f2c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
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
6 conflicts on slot 0xbde9cde546…ae4cff
Audit this contract →
← previous block·next block →recent activity