← previous blocknext block →recent activity
Analyzing
Block #93,502,790
16 transactions · 16 stateful · 2026-08-06 01:31:37 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,502,790 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w210w311w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
8 touches
6 conflicts
0xac8a5059…fd42
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x27279e7f…b1e6
0x34b655…2a6f
4 touches
1 conflict
0x29715fee…dec9
0x34b655…2a6f
4 touches
1 conflict
0x2dd10d87…ecef
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity