← previous blocknext block →recent activity
Analyzing
Block #90,963,195
14 transactions · 12 stateful · 2026-07-28 04:31:50 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,963,195 · 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
2w03w17w28w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2968b5c9…4c9e
0x34b655…2a6f
4 touches
1 conflict
0x2f0fe1df…da89
0x34b655…2a6f
4 touches
1 conflict
0x2f0fe1df…da8a
0x34b655…2a6f
4 touches
1 conflict
0x427d1120…4eb1
0x34b655…2a6f
4 touches
1 conflict
0x5f917ce8…a3c3
0x34b655…2a6f
4 touches
1 conflict
0x6e6b8ec7…2197
0x34b655…2a6f
4 touches
1 conflict
0x6f900be0…cd6e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
1 conflict on slot 0x2968b5c923…a04c9e
Audit this contract →
← previous block·next block →recent activity