← previous blocknext block →recent activity
Analyzing
Block #90,622,245
16 transactions · 14 stateful · 2026-07-26 23:56:32 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,622,245 · 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
4w05w16w17w210w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70cfbacf…5c46
0x34b655…2a6f
8 touches
6 conflicts
0xd19c9d38…b459
0x34b655…2a6f
6 touches
3 conflicts
0x927f7525…9d6e
0x34b655…2a6f
6 touches
3 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0c4ec0fd…5cef
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 0x70cfbacfa4…e85c46
Audit this contract →
← previous block·next block →recent activity