← previous blocknext block →recent activity
Analyzing
Block #93,280,217
8 transactions · 7 stateful · 2026-08-05 06:52:36 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,280,217 · 8 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe999cbf5…d18a
0x34b655…2a6f
4 touches
1 conflict
0x0a42683d…6f4f
0x34b655…2a6f
4 touches
1 conflict
0x0a42683d…6f50
0x34b655…2a6f
4 touches
1 conflict
0x0c3de189…c44b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xd9139645…9af6
0x34b655…2a6f
4 touches
1 conflict
0x5096c6d5…871b
0x34b655…2a6f
3 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
1 conflict on slot 0xe999cbf59e…59d18a
Audit this contract →
← previous block·next block →recent activity