← previous blocknext block →recent activity
Analyzing
Block #90,888,749
13 transactions · 12 stateful · 2026-07-27 22:17:22 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,888,749 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w311w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x3e2663d3…a620
0x34b655…2a6f
4 touches
1 conflict
0x4347b62a…ed5f
0x34b655…2a6f
4 touches
1 conflict
0x475bdffd…9a36
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x63ad92a0…7912
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity