← previous blocknext block →recent activity
Analyzing
Block #90,895,995
19 transactions · 19 stateful · 2026-07-27 22:53:49 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,895,995 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w08w09w310w411w512w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x23d51e55…82c2
0x34b655…2a6f
8 touches
6 conflicts
0xd30f9e74…d404
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xa74d6ebc…fddf
0x34b655…2a6f
7 touches
6 conflicts
0x92385428…6941
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity