← previous blocknext block →recent activity
Analyzing
Block #90,851,078
17 transactions · 16 stateful · 2026-07-27 19:07:49 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,851,078 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w08w19w110w212w113w314w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xb069d064…7ba6
0x34b655…2a6f
6 touches
3 conflicts
0x26d1c221…4d2a
0x34b655…2a6f
6 touches
3 conflicts
0x774b34d3…8da9
0x34b655…2a6f
4 touches
1 conflict
0x9682f4b2…2309
0x34b655…2a6f
4 touches
1 conflict
0xa2bf7bfa…d195
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xb7aced05…46bd
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity