← previous blocknext block →recent activity
Analyzing
Block #90,512,196
12 transactions · 11 stateful · 2026-07-26 14:42:57 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,512,196 · 12 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
5w06w17w28w09w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x085783c4…ec4d
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x2f358e74…1022
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0x8743e1ba…8331
0x34b655…2a6f
4 touches
1 conflict
0xa9af9157…5a6e
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x085783c424…60ec4d
Audit this contract →
← previous block·next block →recent activity