← previous blocknext block →recent activity
Analyzing
Block #90,788,888
29 transactions · 25 stateful · 2026-07-27 13:54:53 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,788,888 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w010w012w113w214w015w116w218w221w122w323w325w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x3dd92584…5d72
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4954a433…820d
0x34b655…2a6f
4 touches
1 conflict
0x57fa2ee5…eec6
0x34b655…2a6f
4 touches
1 conflict
0x74e46435…fdcd
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