← previous blocknext block →recent activity
Analyzing
Block #93,345,767
12 transactions · 11 stateful · 2026-08-05 12:22:10 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,345,767 · 12 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
1w03w14w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
4 touches
1 conflict
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0x78d706d9…2623
0x34b655…2a6f
4 touches
1 conflict
0x3ffb5260…d8fa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1565183a…e0a0
0x34b655…2a6f
2 touches
0 conflicts
0x2ff5b7c6…d8e6
0x34b655…2a6f
2 touches
0 conflicts
0x36d6fb1d…6018
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 0xa6389d470d…f19a28
Audit this contract →
← previous block·next block →recent activity