← previous blocknext block →recent activity
Analyzing
Block #90,967,977
13 transactions · 12 stateful · 2026-07-28 04:55:55 UTC
Parallelism
39/100
Blocked
58%
Avg conflicts / tx
2.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,967,977 · 13 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
4w05w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x705ab4ae…0162
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x4de0baee…27f9
0x34b655…2a6f
6 touches
3 conflicts
0x96d31219…1043
0x34b655…2a6f
6 touches
3 conflicts
0x7ef4ba09…2a25
0x34b655…2a6f
4 touches
1 conflict
0x2a2fcb7f…9ae6
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
28 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity