← previous blocknext block →recent activity
Analyzing
Block #93,925,779
14 transactions · 12 stateful · 2026-08-07 12:58:31 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,925,779 · 14 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
3w04w05w07w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x917f99a5…7989
0x34b655…2a6f
4 touches
1 conflict
0xe3ab4180…f888
0x34b655…2a6f
4 touches
1 conflict
0xfb24441a…4183
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0008
0x04ddf6…7f33
2 touches
0 conflicts
0x446f2734…8b54
0x0a3323…0a3c
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 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity