← previous blocknext block →recent activity
Analyzing
Block #90,510,126
12 transactions · 10 stateful · 2026-07-26 14:32:32 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,510,126 · 12 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
4w05w16w27w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a66856f…8b9f
0x34b655…2a6f
8 touches
6 conflicts
0x57e04406…a617
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
6 touches
3 conflicts
0x8817ea9b…8b07
0x34b655…2a6f
4 touches
1 conflict
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0x88dca381…45aa
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 0x7a66856fea…6a8b9f
Audit this contract →
← previous block·next block →recent activity