← previous blocknext block →recent activity
Analyzing
Block #93,672,628
10 transactions · 9 stateful · 2026-08-06 15:45:23 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,672,628 · 10 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
1w02w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe9452241…95a3
0x34b655…2a6f
4 touches
1 conflict
0x2181494a…83fb
0x34b655…2a6f
4 touches
1 conflict
0x571aa8b4…35fa
0x34b655…2a6f
2 touches
0 conflicts
0x59052228…add7
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
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 0xbbeac3b703…d0c14b
Audit this contract →
← previous block·next block →recent activity