← previous blocknext block →recent activity
Analyzing
Block #93,490,351
14 transactions · 12 stateful · 2026-08-06 00:29:04 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,490,351 · 14 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
5w06w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x785705a8…33e5
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x64f1eb47…cd27
0x34b655…2a6f
4 touches
1 conflict
0x278c4ae5…1639
0x34b655…2a6f
4 touches
1 conflict
0x2741f63d…a456
0x34b655…2a6f
2 touches
0 conflicts
0x282f129e…8f33
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
3 conflicts on slot 0x91b0f8edc5…b76bd7
Audit this contract →
← previous block·next block →recent activity