← previous blocknext block →recent activity
Analyzing
Block #90,611,665
17 transactions · 16 stateful · 2026-07-26 23:03:19 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,611,665 · 17 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
1w02w13w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde9d38a8…4c0f
0x34b655…2a6f
4 touches
1 conflict
0x62593a6d…03d6
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xbc2d4622…e7e9
0x34b655…2a6f
4 touches
1 conflict
0xbe8aeed7…076a
0x34b655…2a6f
4 touches
1 conflict
0xc2a783bf…25e3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd2d3fe13…b827
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
1 conflict on slot 0xde9d38a88f…994c0f
Audit this contract →
← previous block·next block →recent activity