← previous blocknext block →recent activity
Analyzing
Block #90,811,433
16 transactions · 13 stateful · 2026-07-27 15:48:23 UTC
Parallelism
56/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,811,433 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w110w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x7b3f8378…b37d
0x34b655…2a6f
6 touches
3 conflicts
0x185ad6db…d46a
0x34b655…2a6f
4 touches
1 conflict
0x228d47a0…0efa
0x34b655…2a6f
4 touches
1 conflict
0x28653e24…7b35
0x34b655…2a6f
4 touches
1 conflict
0x2b5cb9f0…1d10
0x34b655…2a6f
4 touches
1 conflict
0x41377979…0a18
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity