← previous blocknext block →recent activity
Analyzing
Block #90,977,163
13 transactions · 11 stateful · 2026-07-28 05:42:07 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,977,163 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w18w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd22c5fd0…00f2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe8eae8a3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x01bf3d36…d122
0x34b655…2a6f
4 touches
1 conflict
0x3214a74c…6e92
0x34b655…2a6f
4 touches
1 conflict
0x48965dfe…432b
0x34b655…2a6f
4 touches
1 conflict
0x86977b3d…a9c4
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
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 0xd22c5fd0e4…6a00f2
Audit this contract →
← previous block·next block →recent activity