← previous blocknext block →recent activity
Analyzing
Block #93,347,431
15 transactions · 14 stateful · 2026-08-05 12:30:32 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,347,431 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w26w19w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
6 touches
3 conflicts
0x04e17b28…d9ef
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9f0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3b56f79b…310f
0x34b655…2a6f
4 touches
1 conflict
0x3de29a8d…af0a
0x34b655…2a6f
4 touches
1 conflict
0x6ab1bf20…0e58
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
3 conflicts on slot 0xa6389d470d…f19a28
Audit this contract →
← previous block·next block →recent activity