← previous blocknext block →recent activity
Analyzing
Block #90,944,321
13 transactions · 12 stateful · 2026-07-28 02:56:55 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,944,321 · 13 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
2w05w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7fb89e5…b3c8
0x34b655…2a6f
4 touches
1 conflict
0xc4dc32ca…83f9
0x34b655…2a6f
4 touches
1 conflict
0xd42cf33e…e446
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x6862e825…d6e1
0x34b655…2a6f
4 touches
1 conflict
0x7fbc12f5…085f
0x34b655…2a6f
3 touches
1 conflict
0xcfe06a18…b5b5
0x2b46c0…1669
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 0xb7fb89e532…02b3c8
Audit this contract →
← previous block·next block →recent activity