← previous blocknext block →recent activity
Analyzing
Block #93,671,183
14 transactions · 14 stateful · 2026-08-06 15:38:08 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,671,183 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w38w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b666394…cae1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x5e71af98…bfd6
0x34b655…2a6f
4 touches
1 conflict
0x6d74089c…c836
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x3b6663946d…4ecae1
Audit this contract →
← previous block·next block →recent activity