← previous blocknext block →recent activity
Analyzing
Block #90,223,033
17 transactions · 14 stateful · 2026-07-25 14:13:16 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,223,033 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w19w212w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x86d1a3fb…ed61
0x34b655…2a6f
4 touches
1 conflict
0x8cb33e96…1609
0x34b655…2a6f
4 touches
1 conflict
0x9a7be229…5108
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca011cc9…731f
0x34b655…2a6f
4 touches
1 conflict
0xd8df242f…434f
0x34b655…2a6f
4 touches
1 conflict
0xda65cebb…3038
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 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity