← previous blocknext block →recent activity
Analyzing
Block #90,946,254
14 transactions · 13 stateful · 2026-07-28 03:06:38 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,946,254 · 14 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
4w08w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f3152e8…f181
0x34b655…2a6f
4 touches
1 conflict
0x67b7c4b9…179b
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xea64c16c…c0e8
0x34b655…2a6f
3 touches
1 conflict
0x1c04a22d…d43b
0x065c9d…c394
2 touches
0 conflicts
0x3cae1fb7…74a7
0x065c9d…c394
2 touches
0 conflicts
0x5a330c21…21dd
0x065c9d…c394
2 touches
0 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: Perpl
1 conflict on slot 0x0f3152e867…56f181
Audit this contract →
← previous block·next block →recent activity