← previous blocknext block →recent activity
Analyzing
Block #93,243,638
17 transactions · 14 stateful · 2026-08-05 03:48:40 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,243,638 · 17 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
1w02w13w24w35w36w47w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe10ddee…7510
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x50c0dd87…1128
0x34b655…2a6f
4 touches
1 conflict
0x7aae9795…06ed
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
6 conflicts on slot 0xbe10ddeeb0…ae7510
Audit this contract →
← previous block·next block →recent activity