← previous blocknext block →recent activity
Analyzing
Block #93,368,513
9 transactions · 8 stateful · 2026-08-05 14:16:32 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,368,513 · 9 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
1w02w14w25w06w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aae9795…06ed
0x34b655…2a6f
6 touches
3 conflicts
0xae079c18…933c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4759021d…a62e
0x34b655…2a6f
4 touches
1 conflict
0x04cf93f5…29ce
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x2c390858…b1ed
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
3 conflicts on slot 0x7aae979517…b606ed
Audit this contract →
← previous block·next block →recent activity