← previous blocknext block →recent activity
Analyzing
Block #93,491,101
9 transactions · 8 stateful · 2026-08-06 00:32:50 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,491,101 · 9 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a1d6ba4…ac38
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xa6848351…2238
0x34b655…2a6f
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
2 touches
0 conflicts
0x1f00a5b3…bf76
0x34b655…2a6f
2 touches
0 conflicts
0x376189f6…7cc2
0x34b655…2a6f
2 touches
0 conflicts
0x588ba065…f516
0x34b655…2a6f
2 touches
0 conflicts
0x5d7f309d…5145
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 0x7a1d6ba488…37ac38
Audit this contract →
← previous block·next block →recent activity