← previous blocknext block →recent activity
Analyzing
Block #91,779,519
19 transactions · 18 stateful · 2026-07-31 01:01:45 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,779,519 · 19 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
1w02w16w07w18w29w312w213w414w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xa6f5b3f2…a865
0x34b655…2a6f
10 touches
10 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x70b7b52e…7744
0x34b655…2a6f
6 touches
3 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0x99c5409a…25b7
0x34b655…2a6f
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
6 touches
3 conflicts
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity