← previous blocknext block →recent activity
Analyzing
Block #93,075,040
19 transactions · 16 stateful · 2026-08-04 13:40:08 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,075,040 · 19 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
1w02w15w06w07w19w110w211w313w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x23eeba48…cc52
0x34b655…2a6f
4 touches
1 conflict
0x40ee7a94…d6a8
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x4954a433…820d
0x34b655…2a6f
4 touches
1 conflict
0x542ff3d0…3fa7
0x34b655…2a6f
4 touches
1 conflict
0x84d6407e…6fb2
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity