← previous blocknext block →recent activity
Analyzing
Block #90,893,523
21 transactions · 20 stateful · 2026-07-27 22:41:23 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,893,523 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w09w010w111w012w013w114w116w017w119w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5daadcc…c9b9
0xf9b0c8…8081
4 touches
1 conflict
0x1eef375a…1ed8
0xf9b0c8…8081
4 touches
1 conflict
0x3fdd750b…ac65
0xf9b0c8…8081
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x3d158563…8713
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x75cb8e55…1cd9
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: 0xf9b0c8ee…ea8081
1 conflict on slot 0xd5daadcc22…9bc9b9
Audit this contract →
← previous block·next block →recent activity