← previous blocknext block →recent activity
Analyzing
Block #90,626,517
10 transactions · 10 stateful · 2026-07-27 00:18:02 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,626,517 · 10 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
1w02w14w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08cc321f…91e1
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xf17c63a1…a36b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe74deb99…9e5b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x304a552a…8fc8
0x34b655…2a6f
2 touches
0 conflicts
0x42d5e8f3…5930
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
3 conflicts on slot 0x08cc321f38…d691e1
Audit this contract →
← previous block·next block →recent activity