← previous blocknext block →recent activity
Analyzing
Block #90,770,815
16 transactions · 12 stateful · 2026-07-27 12:23:55 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,770,815 · 16 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
1w02w14w05w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33e1047c…f65a
0x9f3832…4ae4
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xa4b7c8aa…4596
0x9f3832…4ae4
4 touches
1 conflict
0xa4b7c8aa…4597
0x9f3832…4ae4
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x53bc68ea…13ad
0xe1c8b7…3022
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
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: 0x9f383273…514ae4
1 conflict on slot 0x33e1047c86…26f65a
Audit this contract →
← previous block·next block →recent activity