← previous blocknext block →recent activity
Analyzing
Block #90,834,855
16 transactions · 14 stateful · 2026-07-27 17:46:13 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,834,855 · 16 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
1w02w13w05w16w28w29w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb31d278…9107
0x34b655…2a6f
8 touches
6 conflicts
0xf3383813…4a0c
0x34b655…2a6f
6 touches
3 conflicts
0x909def91…71d2
0x851145…3f07
4 touches
1 conflict
0xd537abd7…104a
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x06e6ff87…e712
0x34b655…2a6f
4 touches
1 conflict
0x12d867cc…b97c
0x34b655…2a6f
4 touches
1 conflict
0x4dc6cd61…f674
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
6 conflicts on slot 0xfb31d278a3…299107
Audit this contract →
← previous block·next block →recent activity