← previous blocknext block →recent activity
Analyzing
Block #90,604,915
16 transactions · 16 stateful · 2026-07-26 22:29:21 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,604,915 · 16 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
1w04w05w17w08w19w210w312w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
8 touches
6 conflicts
0x44ed742f…63f5
0x3bd359…433a
8 touches
6 conflicts
0x4eb758b8…b13b
0x3bd359…433a
8 touches
6 conflicts
0x67d846dd…358c
0x526112…7777
8 touches
6 conflicts
0x9527c4ff…73fb
0x526112…7777
8 touches
6 conflicts
0x33e1047c…f65a
0x9f3832…4ae4
8 touches
6 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
8 touches
6 conflicts
0xa4b7c8aa…4596
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