← previous blocknext block →recent activity
Analyzing
Block #90,638,436
13 transactions · 11 stateful · 2026-07-27 01:17:59 UTC
Parallelism
62/100
Blocked
64%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,638,436 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w27w38w411w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b86c265…03e2
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd18e4cb7…88d4
0x34b655…2a6f
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0x4e50038e…6e29
0x34b655…2a6f
4 touches
1 conflict
0x6f8644f7…10fa
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
3 conflicts on slot 0x1b86c265dc…3c03e2
Audit this contract →
← previous block·next block →recent activity