← previous blocknext block →recent activity
Analyzing
Block #93,074,820
58 transactions · 54 stateful · 2026-08-04 13:39:02 UTC
Parallelism
93/100
Blocked
9%
Avg conflicts / tx
0.16
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,074,820 · 58 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w114w015w149w255w256w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x2a34bb88…04d5
0x34b655…2a6f
4 touches
1 conflict
0x2a34bb88…04d6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
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
1 conflict on slot 0x07d8b1e8f0…0978c6
Audit this contract →
← previous block·next block →recent activity