← previous blocknext block →recent activity
Analyzing
Block #93,234,839
9 transactions · 8 stateful · 2026-08-05 03:04:26 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,234,839 · 9 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xa39f5fd2…32e7
0x34b655…2a6f
4 touches
1 conflict
0xba352368…cbf1
0x34b655…2a6f
4 touches
1 conflict
0x03a6363b…ad2b
0x34b655…2a6f
2 touches
0 conflicts
0x1a8b7623…8dec
0x34b655…2a6f
2 touches
0 conflicts
0x1f8eaa5e…7201
0x34b655…2a6f
2 touches
0 conflicts
0x224d6800…4508
0x34b655…2a6f
2 touches
0 conflicts
0x286711a5…b3bf
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity