← previous blocknext block →recent activity
Analyzing
Block #90,819,594
10 transactions · 9 stateful · 2026-07-27 16:29:27 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,819,594 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w17w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0xf18906a6…d2e3
0x34b655…2a6f
4 touches
1 conflict
0x36e357c3…d325
0x34b655…2a6f
4 touches
1 conflict
0x0fffa5c0…a3a9
0xa6afd3…d132
4 touches
1 conflict
0x0a2a1a8a…f83e
0x34b655…2a6f
2 touches
0 conflicts
0x0d67b66f…c9b1
0x34b655…2a6f
2 touches
0 conflicts
0x0f8c9422…1383
0x34b655…2a6f
2 touches
0 conflicts
0x107b89e4…470d
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 0x6713b0185b…1305f3
Audit this contract →
← previous block·next block →recent activity