← previous blocknext block →recent activity
Analyzing
Block #90,771,124
21 transactions · 19 stateful · 2026-07-27 12:25:28 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,771,124 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w311w014w115w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xd7badc5e…8c2b
0xa6afd3…d132
4 touches
1 conflict
0x0f7df08f…cad4
0xa6afd3…d132
4 touches
1 conflict
0x17e90565…d957
0xa6afd3…d132
4 touches
1 conflict
0x9000d2ee…2a11
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity