← previous blocknext block →recent activity
Analyzing
Block #90,788,043
31 transactions · 26 stateful · 2026-07-27 13:50:37 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,788,043 · 31 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
1w02w14w09w010w111w212w313w014w415w118w523w224w126w228w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x89a9e623…61b2
0x34b655…2a6f
4 touches
1 conflict
0x9211e33e…0b61
0x34b655…2a6f
4 touches
1 conflict
0x9d565a45…2377
0x34b655…2a6f
4 touches
1 conflict
0xc148f9cc…0924
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity