← previous blocknext block →recent activity
Analyzing
Block #90,784,403
18 transactions · 13 stateful · 2026-07-27 13:32:17 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,784,403 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w111w212w313w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7032dc14…49ea
0x34b655…2a6f
6 touches
3 conflicts
0x0a005879…de60
0x34b655…2a6f
6 touches
3 conflicts
0x7cfc99cf…59d2
0x34b655…2a6f
4 touches
1 conflict
0x84b1ef7e…8a84
0x34b655…2a6f
4 touches
1 conflict
0x86d77ea5…999e
0x34b655…2a6f
4 touches
1 conflict
0x94bfba91…4d2a
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity