← previous blocknext block →recent activity
Analyzing
Block #90,889,135
28 transactions · 25 stateful · 2026-07-27 22:19:18 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,889,135 · 28 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
1w05w18w09w110w211w312w013w115w016w017w219w022w323w124w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0d488000…3831
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x2cd96bdc…4117
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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: 0x48cba278…e2b48b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity