← previous blocknext block →recent activity
Analyzing
Block #93,280,424
14 transactions · 12 stateful · 2026-08-05 06:53:38 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,280,424 · 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
6w07w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaa48195d…ffee
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x74204a9e…b9d5
0x34b655…2a6f
4 touches
1 conflict
0xa8667a2e…b5e2
0x34b655…2a6f
3 touches
1 conflict
0x0e246445…9e0e
0x34b655…2a6f
3 touches
1 conflict
0x5cc78005…4877
0x34b655…2a6f
2 touches
0 conflicts
0x7175a904…640c
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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity