← previous blocknext block →recent activity
Analyzing
Block #90,854,324
13 transactions · 13 stateful · 2026-07-27 19:24:09 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,854,324 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w18w19w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3fc40da…1c60
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x06cfc5f1…c162
0x34b655…2a6f
2 touches
0 conflicts
0x20ff72d4…5971
0x34b655…2a6f
2 touches
0 conflicts
0x23d265a4…ddd3
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc3fc40dab7…e31c60
Audit this contract →
← previous block·next block →recent activity