← previous blocknext block →recent activity
Analyzing
Block #94,486,530
10 transactions · 8 stateful · 2026-08-09 12:14:51 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,486,530 · 10 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
4w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bc437df…a6c7
0x34b655…2a6f
4 touches
1 conflict
0xbd75d5bc…78f2
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xf17c63a1…a36b
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
0x34b655…2a6f
4 touches
1 conflict
0x4a3026aa…fd65
0x34b655…2a6f
3 touches
1 conflict
0x362b2051…85cc
0x34b655…2a6f
2 touches
0 conflicts
0x388a4c2f…9868
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 0x2bc437df4a…61a6c7
Audit this contract →
← previous block·next block →recent activity