← previous blocknext block →recent activity
Analyzing
Block #93,363,445
23 transactions · 21 stateful · 2026-08-05 13:51:03 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,363,445 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w28w09w112w213w314w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x700c7319…e584
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x8eef368f…aa21
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0d3b978b…5e8e
0x34b655…2a6f
6 touches
3 conflicts
0x50dfdd6a…fc6a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x700c73193c…17e584
Audit this contract →
← previous block·next block →recent activity