← previous blocknext block →recent activity
Analyzing
Block #90,698,563
11 transactions · 11 stateful · 2026-07-27 06:20:28 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,698,563 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
8 touches
6 conflicts
0x12a9b76e…cb76
0x3bd359…433a
8 touches
6 conflicts
0x44ed742f…63f5
0x3bd359…433a
8 touches
6 conflicts
0x4eb758b8…b13b
0x3bd359…433a
8 touches
6 conflicts
0x67d846dd…358c
0x609679…7777
8 touches
6 conflicts
0x02059d37…b643
0x9f3832…4ae4
8 touches
6 conflicts
0x02059d37…b644
0x9f3832…4ae4
8 touches
6 conflicts
0x6faf6baf…150d
0x9f3832…4ae4
8 touches
6 conflicts
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: 0xe1c8b733…e33022
6 conflicts on slot 0xa164d95170…fa1534
Audit this contract →
← previous block·next block →recent activity