← previous blocknext block →recent activity
Analyzing
Block #93,564,046
13 transactions · 12 stateful · 2026-08-06 06:39:32 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,564,046 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe196f841…22e4
0x34b655…2a6f
4 touches
1 conflict
0x3fead0ae…0e35
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe196f841…22e3
0x34b655…2a6f
4 touches
1 conflict
0xfbb1da9b…8a7d
0x34b655…2a6f
3 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
2 touches
0 conflicts
0x327ec3a4…cf8c
0x9f3832…4ae4
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 0xe196f8419b…9322e4
Audit this contract →
← previous block·next block →recent activity